Occurring conflict errors while running the operator, what should I check?

[sykim-etri]

제 개발환경에서 operator를 실행하니 아래와 같이 동일한 Container를 생성하려고 시도하면서 진행이 되지 않는 현상이 있습니다. 혹시 체크해볼 사항이 무엇이 있을까요?

o Ubuntu 18.04.4
o Tested commit: 98f2a54

--아래--

# ./operator run
CB_OPERATOR_MODE: DockerCompose

[Setup and Run Cloud-Barista]

[Config path] ../docker-compose-mode-files/docker-compose.yaml

Creating cb-dragonfly-influxdb ...
Creating cb-dragonfly-etcd ...
Creating cb-tumblebug-phpliteadmin ...
Creating cb-restapigw-jaeger ...
Creating cb-restapigw-influxdb ...
Creating cb-dragonfly-etcd
Creating cb-dragonfly-influxdb
Creating cb-tumblebug-phpliteadmin
Creating cb-restapigw-jaeger
Creating cb-dragonfly-influxdb ... error

ERROR: for cb-dragonfly-influxdb  Cannot create container for service cb-dragonfly-influxdb: Conflict. The container name "/cb-dragonfly-influxdb" is already in use by container "2d15cca0ed2f399ff3155648538Creating cb-tumblebug-phpliteadmin ... error

ERROR: for cb-tumblebug-phpliteadmin  Cannot create container for service cb-tumblebug-phpliteadmin: Conflict. The container name "/cb-tumblebug-phpliteadmin" is already in use by container "6947d55ae3318f3Creating cb-dragonfly-etcd ... error

ERROR: for cb-dragonfly-etcd  Cannot create container for service cb-dragonfly-etcd: Conflict. The container name "/cb-dragonfly-etcd" is already in use by container "c7800abcc11a333f4dcd79eb1527d20a2efc311Creating cb-restapigw-influxdb ... error

ERROR: for cb-restapigw-influxdb  Cannot create container for service influxdb: Conflict. The container name "/cb-restapigw-influxdb" is already in use by container "efc1fb276586b04527c02122dcac736a3d09e100Creating cb-restapigw-jaeger ... error

ERROR: for cb-restapigw-jaeger  Cannot create container for service jaeger: Conflict. The container name "/cb-restapigw-jaeger" is already in use by container "925c76c42780b892036e34b2183fc0c36fabb47e835eda48e4bbc9b83270205d". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for influxdb  Cannot create container for service influxdb: Conflict. The container name "/cb-restapigw-influxdb" is already in use by container "efc1fb276586b04527c02122dcac736a3d09e100bc8c5e9b4e944c0a1a3012eb". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for cb-tumblebug-phpliteadmin  Cannot create container for service cb-tumblebug-phpliteadmin: Conflict. The container name "/cb-tumblebug-phpliteadmin" is already in use by container "6947d55ae3318f3f07c969a1a60d928c3b77e48829e5aaff675b5b8001cc27da". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for jaeger  Cannot create container for service jaeger: Conflict. The container name "/cb-restapigw-jaeger" is already in use by container "925c76c42780b892036e34b2183fc0c36fabb47e835eda48e4bbc9b83270205d". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for cb-dragonfly-etcd  Cannot create container for service cb-dragonfly-etcd: Conflict. The container name "/cb-dragonfly-etcd" is already in use by container "c7800abcc11a333f4dcd79eb1527d20a2efc3116f7c36750d5a366b9a8fa07a6". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for cb-dragonfly-influxdb  Cannot create container for service cb-dragonfly-influxdb: Conflict. The container name "/cb-dragonfly-influxdb" is already in use by container "2d15cca0ed2f399ff31556485385ef577f82eb41d81bc777c4bd71e0a97912da". You have to remove (or rename) that container to be able to reuse that name.
Encountered errors while bringing up the project.

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.57. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[sykim-etri]

아래와 같이 예전에 실행한 후 삭제되지 않았던 Container가 그대로 있어서 나타난 현상이었습니다. ./operator info 명령을 쳤을때 나타나지 않은 Container들이었습니다. 혹시 개선 가능한 문제인지 여유가 될때 검토하면 좋겠습니다.
--아래--

➜  src git:(master) ✗ sudo docker ps -a
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS                      PORTS               NAMES
350fd648dac9        cloudbaristaorg/cb-webtool:v0.2.0     "/bin/sh -c 'reflex …"   3 months ago        Exited (0) 3 months ago                         cb-webtool
72a4ab778e68        cloudbaristaorg/cb-tumblebug:v0.2.0   "/app/src/cb-tumbleb…"   3 months ago        Exited (2) 3 months ago                         cb-tumblebug
bc79791785b1        cloudbaristaorg/cb-spider:v0.2.0      "/root/go/src/github…"   3 months ago        Exited (2) 3 months ago                         cb-spider
81ea8e638b72        cloudbaristaorg/cb-restapigw:v0.2.0   "/app/cb-restapigw -…"   3 months ago        Exited (0) 3 months ago                         cb-restapigw
83d6c427fdaa        cloudbaristaorg/cb-dragonfly:v0.2.0   "./wait-for-it-wrapp…"   3 months ago        Exited (137) 3 months ago                       cb-dragonfly
98824a9a74ad        5eb5f3d7599d                          "/run.sh"                3 months ago        Exited (0) 3 months ago                         cb-restapigw-grafana
c7800abcc11a        bitnami/etcd:3.3.11                   "/entrypoint.sh etcd"    3 months ago        Exited (0) 3 months ago                         cb-dragonfly-etcd
6947d55ae331        acttaiwan/phpliteadmin                "/usr/bin/caddy --co…"   3 months ago        Exited (0) 3 months ago                         cb-tumblebug-phpliteadmin
925c76c42780        5ef5c2d8e8d1                          "/go/bin/all-in-one-…"   3 months ago        Exited (1) 3 months ago                         cb-restapigw-jaeger
efc1fb276586        95750833bc56                          "/entrypoint.sh infl…"   3 months ago        Exited (0) 3 months ago                         cb-restapigw-influxdb
2d15cca0ed2f        95750833bc56                          "/entrypoint.sh infl…"   3 months ago        Exited (0) 3 months ago                         cb-dragonfly-influxdb
➜  src git:(master) ✗ sudo docker rm `docker ps -a -q`

[jihoon-seo]

저는
docker rm 925c76c42780b892036e34b2183fc0c36fabb47e835eda48e4bbc9b83270205d
과 같은 명령을 실행하여
이전 컨테이너를 수동으로 삭제하고 있습니다.

다른 좋은 방법이 있으면 좋을 것 같습니다.

[sykim-etri]

가끔식 발생하는 이슈이긴 한가 봅니다. 간단하게 README의 FAQ 등에 추가하는 방법이 있을 수 있겠네요.