Open j-be opened 2 years ago
I found how to reproduce it:
In a multi-module project (assume you have the modules one
and other
):
cd one
mvn docker:build docker start
cd ../other
mvn docker:stop
Now the container is still there, even though the same project (just a different module) that created it is trying to stop it.
A small reproducer can be found at https://github.com/j-be/fabric8io_docker-maven-plugin_1517
Update: setting docker.allContainers
to true
in pom.xml
, like:
<properties>
<docker.allContainers>true</docker.allContainers>
</properties>
also solves the issue.
Hi @j-be
Where is the description of docker.allContainers?
Description
I'm having the weirdest of errors: After I run my maven builds a couple of times (including failures, which do not clean up the containers) the plugin suddenly fails to stop the container.
mvn docker:stop -X
gives:Notice the missing:
After deleting the container manually and starting over everything is back to normal. Then it works for a couple of runs, and out of nowhere it starts failing again.
I did NOT yet find a way to reproduce it deterministically.See comment below.My config:
and in
pluginManagement
:Info
mvn -v
) :README.me
hereREADME.md
for steps how to reproduce.