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
Since upgrading to Docker 1.8.2 on CentOS 7, we have started to see warnings related to the deletion of images in the maven output. The result of the failure is that the clean operation does not correctly delete images as expected.
Conflict, cannot delete image b17225d77c2be1ff2bbd5590c250873c26759f3de985a63e4346151eb4a04a66 because it is tagged in multiple repositories, use -f to force
The error is due to the fact that the image with the specific ID is tagged with multiple names in the local image repository. The Docker documentation now explains that removal of an image which has multiple tags should use the --force option or the client should remove each of the tags by name via the rmi command.
One solution would be to change the docker-maven-plugin to use --force internally. Alternately, the docker-maven-plugin could track the tags it creates by name and remove them individually during a clean operation.
The text was updated successfully, but these errors were encountered:
Sorry I didn't see your message until now. I just got back from vacation. Thanks for making the fix. I've been using your plugin a lot and though I missed this opportunity, I will probably end up making a contribution at some point.
Since upgrading to Docker 1.8.2 on CentOS 7, we have started to see warnings related to the deletion of images in the maven output. The result of the failure is that the clean operation does not correctly delete images as expected.
The error is due to the fact that the image with the specific ID is tagged with multiple names in the local image repository. The Docker documentation now explains that removal of an image which has multiple tags should use the
--force
option or the client should remove each of the tags by name via thermi
command.One solution would be to change the docker-maven-plugin to use
--force
internally. Alternately, the docker-maven-plugin could track the tags it creates by name and remove them individually during a clean operation.The text was updated successfully, but these errors were encountered: