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
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.
Description
with the following Dockerfile
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.
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 togcr
.I have tried multiple variation of specifying
<pullRegistry>
or separating thedocker:build
anddocker:push
steps. But dmp insists on attempting an unwanted push togcr
.How can we suppress this attempt? Previous versions of dmp did not have this behaviour.
Info
0.45.1
mvn -v
) :3.9.9
27.2.0
The text was updated successfully, but these errors were encountered: