Hello,
i upgrade to 5.9.1 and system didn’t start up with the following error:
RCSTACK: v5.29.1, running rhodecode stack command
+] Running 14/15
Container rc_cluster_apps-vcsserver-3 Started 1.0s
Container rc_cluster_apps-rhodecode-3 Created 0.2s
Container rc_cluster_apps-rhodecode-1 Started 0.5s
Container rc_cluster_apps-vcsserver-1 Started 0.5s
⠴ Container rc_cluster_apps-rhodecode-2 Starting 1.0s
Container rc_cluster_apps-vcsserver-2 Started 0.8s
Container rc_cluster_apps-sshd-2 Created 0.1s
Container rc_cluster_apps-celery-beat-1 Created 0.1s
Container rc_cluster_apps-celery-1 Created 0.1s
Container rc_cluster_apps-svn-3 Created 0.2s
Container rc_cluster_apps-celery-3 Created 0.1s
Container rc_cluster_apps-svn-1 Created 0.1s
Container rc_cluster_apps-celery-2 Created 0.1s
Container rc_cluster_apps-svn-2 Created 0.1s
Container rc_cluster_apps-sshd-1 Created 0.2s
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint rc_cluster_apps-rhodecode-2 (8a836e84
fc8db05982d6b433237474702e74d866d69e63c726a7e83bb7cbb3ed): Bind for 0.0.0.0:10020 failed: port is already allocated
I could fix it due to modification of .custom/docker-compose-apps.override.yaml and reducing the number of worker to 1 in services:
rhodecode:
deploy:
# set number of instances of services to be spawned on stack start replicas: 1
Hi,
did you modify the custom/docker-compose-apps.override.yaml to expose the port to public ?
Yes, i had.
That was the problem.
Thank you !