fix: stacker convert should include ENV vars into the runtime config. - #784
Open
jmblatten wants to merge 1 commit into
Open
fix: stacker convert should include ENV vars into the runtime config.#784jmblatten wants to merge 1 commit into
jmblatten wants to merge 1 commit into
Conversation
Dockerfile ENV defines variables for both build and runtime. Stacker convert, converts ENV for build, but does not include runtime. Stacker uses "environment:" in yaml to define variables for runtime. So, include the ENV variables there so they will show up in the config when running the container. Signed-off-by: Joy Latten <joylatten@geico.com>
jmblatten
requested review from
hallyn,
mikemccracken,
raharper,
rchamarthy,
rchincha,
smoser and
tych0
as code owners
August 5, 2026 20:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dockerfile ENV defines variables for both build and runtime. Stacker convert, converts ENV for build, but does not include runtime. Stacker uses "environment:" in yaml to define variables for runtime. So, include the ENV variables there so they will show up in the config when running the container.
See https://docs.docker.com/reference/dockerfile/#env
What type of PR is this?
bug
Which issue does this PR fix:
#757
What does this PR do / Why do we need it:
See above.
If an issue # is not available please add repro steps and logs showing the issue:
#757
Steps:
Dockerfile contents:
Converted stacker.yaml
Using skopeo inspect
Note: env does not include HELLO and GOODBYE in image.
Testing done on this change:
Dockerfile contents:
Converted stacker.yaml contents
Using skopeo inspect,
Automation added to e2e:
None
Will this break upgrades or downgrades?
No
Does this PR introduce any user-facing change?:
Yes, but only for converted Dockerfiles. The resulting stacker.yaml file will now include an environment section if there were any ENVs in the Dockerfile. This will cause the image runtime to include the environment variables.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.