You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a scenario where it would be very useful to disable image pushing for a specific image.
Given the following skaffold.yaml (excerpt):
apiVersion: skaffold/v3kind: Configbuild:
artifacts:
- image: base-buildcontext: .docker:
dockerfile: base/Dockerfile.build
- image: base-releasecontext: .docker:
dockerfile: base/Dockerfile.release
- image: my-appcontext: .docker:
dockerfile: my-app/Dockerfilerequires:
- image: base-buildalias: BASE_BUILD
- image: base-releasealias: BASE_RELEASE
... more app builds which all use the base-build and base-release images.
And my-app/Dockerfile:
ARG BASE_BUILD
ARG BASE_RELEASE
FROM $BASE_BUILD as build
.. steps to build the app
FROM $BASE_RELEASE as release
COPY --from=build /build/dist/bin/my-app /usr/local/bin/my-app
The base-build image is always uploaded, but it doesn't have to be. It's never used as a release stage of a multi-stage app Dockerfile so the layers cannot be re-used. The build image is quite large (gigabytes) because it has a huge amount of compilers and lib*-dev's installed. Uploading it takes a long time for developers using the setup.
It would be great if there could be some kind of build.artifacts[0].push: Never to override the build.local.push value for a specific artifact/image.
I'd be happy to work on this once we have a good design/specs for it.
The text was updated successfully, but these errors were encountered:
GeertJohan
changed the title
Override pushing per image
Disable image push after build for a specific image
Dec 15, 2022
I have a scenario where it would be very useful to disable image pushing for a specific image.
Given the following skaffold.yaml (excerpt):
And
my-app/Dockerfile
:The
base-build
image is always uploaded, but it doesn't have to be. It's never used as a release stage of a multi-stage app Dockerfile so the layers cannot be re-used. The build image is quite large (gigabytes) because it has a huge amount of compilers and lib*-dev's installed. Uploading it takes a long time for developers using the setup.It would be great if there could be some kind of
build.artifacts[0].push: Never
to override thebuild.local.push
value for a specific artifact/image.I'd be happy to work on this once we have a good design/specs for it.
The text was updated successfully, but these errors were encountered: