Skip to content
New issue

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

Feature request: push multiple stages #2253

Open
LittleFox94 opened this issue Sep 16, 2022 · 1 comment
Open

Feature request: push multiple stages #2253

LittleFox94 opened this issue Sep 16, 2022 · 1 comment
Labels
area/cli bugs related to kaniko CLI area/registry For all bugs having to do with pushing/pulling into registries kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@LittleFox94
Copy link

Hi,

we have a Dockerfile with two stages, prod and dev, where dev builds on top of the prod stage and adds some more stuff for debugging, roughly like this:

FROM python:3.10-slim AS prod

RUN apt-get update && apt-get install ... && apt-get clean && rm -rf /var/lib/apt/lists/*

RUN useradd [..] app
USER app

COPY app/ /app
ENTRYPOINT ["/app/entrypoint"]

FROM prod AS dev
USER root
RUN apt-get update && apt-get install jq curl && [...]

USER app

It would be really great to have them built in one go, instead of rebuilding prod, pull it from the registry or pulling it from the cache. Something like this could work, = isn't allowed in the destination name, so this also shouldn't break any existing usage:

executor --destination prod=$our_registry/foo/bar --destination dev=$another_registry/foo/bar

Thanks for considering :)

@LittleFox94
Copy link
Author

This could also be limited to stages that are already in the build workflow for the selected --target, so we'd have to add --target dev but before it executes the FROM prod AS dev, it would push the current state to the prod destination

@aaron-prindle aaron-prindle added kind/feature-request area/registry For all bugs having to do with pushing/pulling into registries area/cli bugs related to kaniko CLI priority/p2 High impact feature/bug. Will get a lot of users happy priority/p3 agreed that this would be good to have, but no one is available at the moment. and removed priority/p2 High impact feature/bug. Will get a lot of users happy labels Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli bugs related to kaniko CLI area/registry For all bugs having to do with pushing/pulling into registries kind/feature-request priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Development

No branches or pull requests

2 participants