Compose: Renaming a container with the same name as its current name

[zffocussss]

Description of the issue

I use docker-compose to running service with a docker-compose.yml.
(python service,mongo,redis)
everytime python codes are updated,it will be run.
docker-compose build --build-arg
docker-compose up -d --remove-orphans

Context information (for bug reports)

Output of docker-compose version

docker-compose version 1.23.2, build 1110ad01

Output of docker version

Client:
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.6
 Git commit:        6247962
 Built:             Sun Feb 10 04:13:50 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:42:13 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Output of docker-compose config
(Make sure to add the relevant -f and other flags)

(paste here)

Steps to reproduce the issue

this error disappeared when I rerun the same process (I use bitbucket to do this)

Observed result

Expected result

Stacktrace / full error message

I am running a service and have a container name (abc).

ERROR: for abc  Renaming a container with the same name as its current name

Additional information

Host Ubuntu 16.04

[zffocussss]

[zffocussss]

It's my first time to meet this error.Can somebody help me?

[jcsirot]

Hello @zffocussss Could you post a compose file and the list of commands which for which you were able to reproduce the issue?

[NicolasDorier]

just want to report, got same error once on same docker-compose version.
It happened once on many deployment, I don't know if I will be able to reproduce, down and up fixed the situation.

[NicolasDorier]

Docker version 18.09.5, build e8ff056
docker-compose version 1.23.2, build 1110ad01

[NicolasDorier]

Additional info: I did not do build, it was just a docker-compose up.

[kai-chu]

I met the problem as well when I try to run two commands docker-compose up in parallel.
docker-compose version 1.21.0, build 5920eb0

[uptownhr]

I have also started to experience this. I have not changed anything though. Just started happening.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it had not recent activity during the stale period.

[mmathys]

I have this issue