-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[Bug] Args not resolved in multi-stage build #1911
Comments
Related: #1160 |
I see that here Shouldn't it look also in the build args (for what stands "allowed args" ?) } else {
args := ba.GetAllAllowed()
if value, ok := args[resolvedKey]; ok {
resolvedValue = &value
}
meta := ba.GetAllMeta()
if value, ok := meta[resolvedKey]; ok {
resolvedValue = &value
}
} |
4 tasks
gabyx
added a commit
to gabyx/kaniko
that referenced
this issue
Feb 7, 2022
- Building multi-stage Dockerfiles did not correctly resolve ARG commands over different stages. Now, each stage depends on the build arguments set by the stage before. Closes: GoogleContainerTools#1911
gabyx
added a commit
to gabyx/kaniko
that referenced
this issue
Feb 8, 2022
- Building multi-stage Dockerfiles did not correctly resolve ARG commands over different stages. Now, each stage depends on the build arguments set by the stage before. Closes: GoogleContainerTools#1911
gabyx
added a commit
to gabyx/kaniko
that referenced
this issue
Feb 8, 2022
- Building multi-stage Dockerfiles did not correctly resolve ARG commands over different stages. Now, each stage depends on the build arguments set by the stage before. Closes: GoogleContainerTools#1911
tejal29
pushed a commit
that referenced
this issue
Feb 10, 2022
* Fix resolving argument over mulit-stage build - Building multi-stage Dockerfiles did not correctly resolve ARG commands over different stages. Now, each stage depends on the build arguments set by the stage before. Closes: #1911 * Fix resolving empty arg commands
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behavior
Accessing
ARG
s in previous stages are not resolved correctly.Expected behavior
They should be resolved.
To Reproduce
Build without specifying
--build-arg="..."
.Result:
custom::
. ($NAME
is empty) but should be1234
)Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: