dy-sidecar issue: sometimes containers are created but not started

[sanderegg]

Sometimes containers get created but not started.

The dynamic sidecar shows the following error:

:  99%|█████████▉| 992M/999M [00:47<00:00, 20.2Mbyte/s]
decompressing /tmp/tmpb64fspox/workspace.zip:temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5 -> /dy-volumes/home/jovyan/work/workspace/temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5
: 100%|█████████▉| 994M/999M [00:48<00:00, 20.1Mbyte/s]
decompressing /tmp/tmpb64fspox/workspace.zip:temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5 -> /dy-volumes/home/jovyan/work/workspace/temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5
: 100%|█████████▉| 996M/999M [00:48<00:00, 20.2Mbyte/s]
decompressing /tmp/tmpb64fspox/workspace.zip:temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5 -> /dy-volumes/home/jovyan/work/workspace/temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5
: 100%|█████████▉| 999M/999M [00:48<00:00, 20.9Mbyte/s]
decompressing /tmp/tmpb64fspox/workspace.zip:temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5 -> /dy-volumes/home/jovyan/work/workspace/temp/outputs/.Catspine3.smash.00b049a4-e5bd-42ba-8385-dad61da07fd5
: 100%|██████████| 999M/999M [00:48<00:00, 21.7Mbyte/s]

decompressing /tmp/tmpb64fspox/workspace.zip -> /dy-volumes/home/jovyan/work/workspace [8 files/2.927GiB]
: 100%|██████████| 8/8 [01:55<00:00, 15.32s/file]
decompressing /tmp/tmpb64fspox/workspace.zip -> /dy-volumes/home/jovyan/work/workspace [8 files/2.927GiB]
: 100%|██████████| 8/8 [01:55<00:00, 14.38s/file]
ERROR:simcore_service_dynamic_sidecar.api.containers:Marked sidecar as unhealthy, see below for details
:Finished docker-compose up with output
The Docker Engine you're using is running in swarm mode.
Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.
To deploy your application across the swarm, use `docker stack deploy`.
Creating dy-sidecar-68597dad-fd7d-4966-b316-561653c8d369-0-jupyter-smash ... 
ERROR: for dy-sidecar-68597dad-fd7d-4966-b316-561653c8d369-0-jupyter-smash  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
ERROR: for dy-sidecar-68597dad-fd7d-4966-b316-561653c8d369-0-jupyter-smash  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

and the container is actually locked in Created state.

A workaround is to select the container in portainer, and press Start