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.

Sign up for GitHub

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

Jump to bottom

[Dockerfile] Resolve envvar when ENV inherited from parent image #14

Closed
r2d4 opened this issue Jan 31, 2018 · 1 comment
Closed

[Dockerfile] Resolve envvar when ENV inherited from parent image #14

r2d4 opened this issue Jan 31, 2018 · 1 comment
Labels
area/build kind/bug Something isn't working priority/p3 agreed that this would be good to have, but no one is available at the moment.

Comments

@r2d4
Copy link
Contributor

r2d4 commented Jan 31, 2018

We don't currently support the scenario when an ENV is inherited from the parent image and then used in the source of a COPY or ADD. As a short term solution, we can add the entire context, but we might want to figure out a way to resolve those ENVs without adding everything.
@dlorenc dlorenc added kind/bug Something isn't working and removed kind/feature-request labels Jul 2, 2018
@balopat
Copy link
Contributor

balopat commented Aug 21, 2018

/cc @nkubala can you take a look if this is still an issue?

@balopat balopat added the priority/p3 agreed that this would be good to have, but no one is available at the moment. label Aug 21, 2018
@nkubala nkubala closed this as completed Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/build kind/bug Something isn't working priority/p3 agreed that this would be good to have, but no one is available at the moment.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@balopat @r2d4 @dlorenc @nkubala