[
https://issues.apache.org/jira/browse/SLING-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641157#comment-17641157
]
Robert Munteanu edited comment on SLING-11701 at 11/30/22 8:43 AM:
-------------------------------------------------------------------
This should have been fixed with [PR
#81|https://github.com/apache/sling-org-apache-sling-starter/pull/81] .
[~enorman] - please reopen if you still see the problem.
was (Author: rombert):
This should have been fixed with [PR
#81|https://github.com/apache/sling-org-apache-sling-starter/pull/81] .
[~enorman] - please reopen if you still se the problem/
> Starter CI builds are sometimes failing with an error about a conflict with
> the docker container name
> -----------------------------------------------------------------------------------------------------
>
> Key: SLING-11701
> URL: https://issues.apache.org/jira/browse/SLING-11701
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Starter 13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The CI builds are sometimes failing with an error about a conflict with the
> docker container name
> *
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/]
> This error is logged:
> {noformat}
> [ERROR] DOCKER> I/O Error [Unable to create container for
> [apache/sling:snapshot] : {"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)]
> {noformat}
> The docker-maven-plugin documentation indicates that the containerNamePattern
> configuration is what determines the container name being launched.
> * [https://dmp.fabric8.io/#container-name]
> The documentation states that the default containerNamePattern value is
> "%n-%i". The "%i" segment of the pattern is supposed to be an index which is
> incremented if a container has already been created. But this doesn't seem
> to be working for us, so maybe a different value would work more reliably?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
