Hi Robert, I have filed SLING-11701 for tracking the problem. I see today that the last 2 (timer triggered) starter builds have failed again with the same error message about the docker container name conflict.
Regards, Eric On Fri, Nov 25, 2022 at 7:55 AM Robert Munteanu <[email protected]> wrote: > Hi Eric, > > On Wed, 2022-11-23 at 11:47 -0800, Eric Norman wrote: > > I got distracted by the error below from the starter ci build after > > updating to the released versions. I retried the ci starter build > > today > > and the conflict seems to have resolved itself and the build worked. > > Maybe > > something could be done to ensure that the docker container name is > > more > > unique for each test run? > > > > Caused by: > > io.fabric8.maven.docker.access.hc.http.HttpRequestException: > > {"message":"Conflict. The container name \"/sling-1\" is already in > > use by container > > \"561df86f937afdecddc271bf24a537c182c98bc266337e5eee0b679423710689\". > > You have to remove (or rename) that container to be able to reuse > > that > > name."} (Conflict: 409) > > Can you please file a Jira issue? I took a quick look at the plugin > configuration but I did not figure out where this is controlled. > > Thanks, > Robert > >
