We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can specify an output_groups=tarball in my skaffold template to use the tarball from an oci_load bazel target.
output_groups=tarball
oci_load
The oci_load run script is assumed to be the tarball and the output_groups is ignored for the tar ball path. https://github.com/GoogleContainerTools/skaffold/blob/main/pkg/skaffold/build/bazel/build.go#L140
output_groups
# Builds the container image build: artifacts: - image: service bazel: target: //path:image.tar args: - "output_groups=tarball"
I worked around this by defining a filegroup and having skaffold point to that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
I can specify an
output_groups=tarball
in my skaffold template to use the tarball from anoci_load
bazel target.Actual behavior
The
oci_load
run script is assumed to be the tarball and theoutput_groups
is ignored for the tar ball path.https://github.com/GoogleContainerTools/skaffold/blob/main/pkg/skaffold/build/bazel/build.go#L140
Information
Steps to reproduce the behavior
Workaround
I worked around this by defining a filegroup and having skaffold point to that.
The text was updated successfully, but these errors were encountered: