[DP-714] Sporadic error launching backend container due to conflict with himself

[MithunKinarullathil]

Have you checked our docs before proceeding?

• [x] Documentation
• [x] Discourse

Issue Description

Sporadic error launching backend container due to conflict with himself

Steps to Reproduce

1. Install the movai-flow 1.2.0-1
2. Lauch the IDE using the desktop icon
3. Confirm error on the terminal

Actual Behaviour

MOV.AI Flow Launcher: This terminal window will verify all MOVAI Flow services are running and then launch the web application
MOV.AI Flow Launcher: (U) [^_^] (U)
MOV.AI Flow Launcher: Sourcing fleet configuration
/usr/share/movai-flow ~
MOV.AI Flow Launcher: Downloading images
Pulling redis-master ... done
Pulling redis-local  ... done
Pulling backend      ... done
Pulling ros-master   ... done
Pulling spawner      ... done
Pulling haproxy      ... done
MOV.AI Flow Launcher: Starting services
Recreating redis-master-robot1 ... 
haproxy-robot1 is up-to-date
Recreating redis-master-robot1 ... done
Creating backend-robot1        ... error

ERROR: for backend-robot1  Cannot create container for service backend: Conflict. The container name "/backend-robot1" is already in use by container "1ce014ed91eb0cdfab1a9ead45c4b5e203948245321affe8b20d6af1e34dde0b". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for backend  Cannot create container for service backend: Conflict. The container name "/backend-robot1" is already in use by container "1ce014ed91eb0cdfab1a9ead45c4b5e203948245321affe8b20d6af1e34dde0b". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
MOV.AI Flow Launcher: waiting for spawner
MOV.AI Flow Launcher: waiting for spawner

Expected Behaviour

No errors when launching the IDE

Screenshots/GIFs

test@test-VirtualBox:~$ docker ps -a
CONTAINER ID   IMAGE                                                      COMMAND                  CREATED         STATUS                   PORTS                                                                            NAMES
9105f15ea7df   pubregistry.aws.cloud.mov.ai/ce/ros-master-noetic:v1.0.0   "docker-entrypoint.sh"   7 minutes ago   Up 7 minutes (healthy)   0.0.0.0:11311->11311/tcp, :::11311->11311/tcp                                    ros-master-robot1
60991f97368a   pubregistry.aws.cloud.mov.ai/ce/redis2:v1.0.6              "movai-entrypoint.sh…"   7 minutes ago   Up 7 minutes (healthy)   0.0.0.0:6379->6379/tcp, :::6379->6379/tcp                                        redis-master-robot1
1ce014ed91eb   pubregistry.aws.cloud.mov.ai/ce/backend-noetic:1.0.0.20    "docker-entrypoint.sh"   7 minutes ago   Up 7 minutes (healthy)                                                                                    backend-robot1
2ed9f7b8dcbc   haproxy:2.4.15                                             "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes             0.0.0.0:8080->80/tcp, :::8080->80/tcp, 0.0.0.0:8443->443/tcp, :::8443->443/tcp   haproxy-robot1
302b29c380ff   pubregistry.aws.cloud.mov.ai/ce/redis2:v1.0.6              "movai-entrypoint.sh…"   7 minutes ago   Up 7 minutes (healthy)   0.0.0.0:6380->6379/tcp, :::6380->6379/tcp                                        redis-local-robot1

Versions

• movai-flow: 1.2.0-1
• movai-ide: N/A

Possible workarounds

• movai-flow-stop
• movai-flow-launch (then it is started with success)

Additional Details

• Installed packages: N/A

[guide-bot[bot]]

Thanks for opening this Issue! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.