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
Changing an ARG that is used in a later ENV statement will not break the cache. The issue was reported in #5095. The argument it was closed was that buildkit behaves the same way. In my testing buildkit has fixed or is not showing this behaviour any more.
both hashes are the same. When running the container after each command (podman run --rm -it envtest and then env) it will show the STAGE environment as being "stage1" and not change to stage2
When running with buildkit v0.12.3 (which is packaged in my Docker on Mac installation):
Description
Follow up to #5095.
Changing an ARG that is used in a later ENV statement will not break the cache. The issue was reported in #5095. The argument it was closed was that buildkit behaves the same way. In my testing buildkit has fixed or is not showing this behaviour any more.
Steps to reproduce the issue:
both hashes are the same. When running the container after each command (
podman run --rm -it envtest
and thenenv
) it will show the STAGE environment as being "stage1" and not change to stage2When running with buildkit v0.12.3 (which is packaged in my Docker on Mac installation):
This will produce two different hashes and when running the containers in between they will have the correct STAGE environment variable value.
Describe the results you received:
STAGE environment variable does not change between the container builds.
Describe the results you expected:
STAGE environment variable
Output of
podman version
if reporting apodman build
issue:The text was updated successfully, but these errors were encountered: