-
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
Cannot temporarily tag because target image already exists #838
Comments
Please remove this codeline as the user's docker version tag will take care of replacing it OR failing to let the user know of an existing tag image. |
Just hit this problem after changing my config from
to
Is one way correct and one way wrong? |
I am having this issue as well on several projects, but not on others. Is there any update to the status of the code that @NancyChunlan pasted above? |
@gnboorse I didn't get any update yet, as workaround, we use script to remove target images before the plugin. |
@NancyChunlan we ended up moving away from this plugin actually. We are now doing the docker and java builds separately. |
Sorry for the super late response, not sure why this issue was below my radar. I agree that we should be more conservative here and I'm going to tackle this for the next release. |
…one by the registry just fine.
…one by the registry just fine.
@rhuss |
Fixes fabric8io#838 There are a few reasons why such a tag might exist: * Previous run was killed part way through push tag, resulting in the finally block not running * In my case, was previously manually tagging and pushing, but I didn't clean up old tags, then I switched to using Fabric8 At any rate, I see no harm in overwriting the tag, since if doing it manually, that's what you'd do anyway.
Fixes fabric8io#838 There are a few reasons why such a tag might exist: * Previous run was killed part way through push tag, resulting in the finally block not running * In my case, was previously manually tagging and pushing, but I didn't clean up old tags, then I switched to using Fabric8 At any rate, I see no harm in overwriting the tag, since if doing it manually, that's what you'd do anyway. Signed-off-by: James Roper <[email protected]>
Fixed in #1170. |
Add three global templates needed to build multiarch images: - {project-name}-docker-manifest-{stream}: creates a docker manifest list with images for multiple architectures by calling docker_push_manifest.sh - {project-name}-multiarch-docker-stage-{stream}: multijob that uses the global-jjb template {project-name}-maven-docker-stage-{stream} to produce staging images for each supported arch and a manifest list for them - {project-name}-multiarch-{stream}-merge-java: multijob that uses the existing {project-name}-{stream}-merge-java template to produce snapshot images for each suppported arch and a manifest list for them The policy/docker project jobs are modified to use the new multiarch templates. All images are now pushed to DockerHub instead of Nexus (as Nexus lacks support for docker manifest list). Cancel the triggers for child jobs, as they will be triggered by the parent multiarch job. For the jobs that build images, use registry registry-1.docker.io as a workaround for [1]. Enable the multiarch jobs only for the master branch for now. [1] fabric8io/docker-maven-plugin#838 Issue-ID: CIMAN-217 Change-Id: Ibd00d24bb70ef51f761005016b7baea4ef66a0a5 Signed-off-by: Paul Vaduva <[email protected]> Signed-off-by: Cristina Pauna <[email protected]> Signed-off-by: Alexandru Avadanii <[email protected]>
when can we expect this to available in https://mvnrepository.com/artifact/io.fabric8/docker-maven-plugin
|
Hmm, I think most probably around Christmas. But Roland can answer it more precisely since he maintains it |
I will try to make a release before the end of the week, or early next week. Sorry for the delay, year end stress here :) |
Hi @rhuss when do you think it can be released and will available in https://mvnrepository.com/? |
Sorry, PTO was more vacation than expected ;-) But now that I'm back on track, I'm already preparing the release so should be out at latest at the end of this week. |
This issue is still observed occasionally in latest release v0.33.0 |
Hi, I am also facing this error in v0.33.0. |
Could you please post a sample project so that could be reproduced ? |
This issue is observed occasionally, or I can even say "rarely". The related projects are very common, nothing special. |
As checked, 0.32.0 has fixed this issue.
|
This issue happened when we have the image tagged with docker registry, and if we tried to tag a new image with the same tag (with docker registry) for docker:push, it will be failed. |
Hi, |
Sometimes when we have target image already existing in system, and so caused the docker-maven-plugin failed to temporarily tag. After checked, found following code.
I guess it's abnormal to interrupt the docker push with such errors, is it possible to remove the exception or add a parameter to toggle on/off the exception?
The text was updated successfully, but these errors were encountered: