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.

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 failures with buildx due forced push attempts #1835

Open
duncdrum opened this issue Nov 2, 2024 · 0 comments
Open

Build failures with buildx due forced push attempts #1835

duncdrum opened this issue Nov 2, 2024 · 0 comments

Comments

@duncdrum
Copy link

duncdrum commented Nov 2, 2024

Description

with the following Dockerfile

FROM gcr.io/distroless/java17:latest
...

we are pulling the base image for our build from googles container registry. The final image should then be pushed to docker's container registry.

However the dmp plugin fails our builds, with the following message.

[INFO] DOCKER> ERROR: failed to solve: failed to push gcr.io/existdb/...

Setting the <pushRegistry> works. So images are pushed to docker.io, but our CI consistently fails because of the attempted push to google container registry. We do not want to push to gcr.

I have tried multiple variation of specifying <pullRegistry> or separating the docker:build and docker:push steps. But dmp insists on attempting an unwanted push to gcr.

How can we suppress this attempt? Previous versions of dmp did not have this behaviour.

Info

  • docker-maven-plugin version : 0.45.1
  • Maven version (mvn -v) : 3.9.9

line-o pushed a commit to line-o/exist that referenced this issue Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant