-
Notifications
You must be signed in to change notification settings - Fork 645
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
Build arg regression with 0.44.0 #1756
Comments
@mattnelson : Thanks for reporting, I can reproduce this issue. I'll try to fix it . |
In #1731 source of buildArgs was changed to use build args from maven/system properties. But using that dropped the source from build configuration, which caused this regession. |
…ile pulling images (fabric8io#1756) Fixes regression introduced by fabric8io#1731 In fabric8io#1731, we added support for specifying docker build args from maven/system properties. However, I missed it in review that build args specified in plugin image build configuration are no longer passed to autoPullBaseImage. Ensure we merge image build configuration build args with args provided via maven/system properties before passing them to autoPullBaseImage Signed-off-by: Rohan Kumar <[email protected]>
…ile pulling images (fabric8io#1756) Fixes regression introduced by fabric8io#1731 In fabric8io#1731, we added support for specifying docker build args from maven/system properties. However, I missed it in review that build args specified in plugin image build configuration are no longer passed to autoPullBaseImage. Ensure we merge image build configuration build args with args provided via maven/system properties before passing them to autoPullBaseImage Signed-off-by: Rohan Kumar <[email protected]>
…ile pulling images (fabric8io#1756) Fixes regression introduced by fabric8io#1731 In fabric8io#1731, we added support for specifying docker build args from maven/system properties. However, I missed it in review that build args specified in plugin image build configuration are no longer passed to autoPullBaseImage. Ensure we merge image build configuration build args with args provided via maven/system properties before passing them to autoPullBaseImage Signed-off-by: Rohan Kumar <[email protected]>
…ile pulling images (#1756) Fixes regression introduced by #1731 In #1731, we added support for specifying docker build args from maven/system properties. However, I missed it in review that build args specified in plugin image build configuration are no longer passed to autoPullBaseImage. Ensure we merge image build configuration build args with args provided via maven/system properties before passing them to autoPullBaseImage Signed-off-by: Rohan Kumar <[email protected]>
@mattnelson : I've merged changes that are supposed to fix this issue. Could you please try out Docker Maven Plugin Snapshots and see if it fixes your issue. |
We need to downgrade to 0.43.4 again because of this regression: fabric8io/docker-maven-plugin#1756 Once they release a new version, try again.
Fixes it for me. Before:
With
|
@poikilotherm : Thanks for trying it out. I also need to check #1778 if it's related, then I'll try to cut a new release. |
Same regression from Can the issue be reopened ? EDIT:
|
@ggjulio : I haven't released a new version since this change got merged. You might want to verify on 0.45-SNAPSHOT ( try Docker Maven Plugin Snapshots and see if it fixes your issue.) |
Nice, it fixes the issue. Thank you ! |
@ggjulio : Sorry for the delay, I'll try to cut 0.45.0 by the end of this month. |
Hi @rohanKanojia, do you have a new estimated date for the next release ? |
@ggjulio : I'm really sorry for the delay. I will try to cut a release this week. |
Description
Build arg regression with 0.44.0, possibly from #1731
Info
docker-maven-plugin version : 0.44.0
Maven version (
mvn -v
) : 3.9.6Docker version : Docker version 24.0.7-rd, build 72ffacf
If it's a bug, how to reproduce :
Have a dockerfile that uses a build arg for the FROM image.
Flex that build arg via the plugin configuration stanzas.
Partial Workaround
Running the build with
mvn package -DFROM_IMAGE=openjdk:21
works, but is only a viable workaround when building a single image for the entire build.The text was updated successfully, but these errors were encountered: