reslesno.blogg.se

It seems that the ordering is somehow not observed, that is, services that depend on the log service try to start up before syslog is fully up and running, but give up early, when they find that they cannot reach syslog. docker-compose.yml -f up -d works fine. Manually starting harbor via docker-compose -f.

observe docker ps -a and see that only some containers reach Up status.

Note about my setup: I'm running harbor behind nginx as a reverse proxy, as explained in #3114 (main changes: port of proxy service, public_url fixup in prepare script, X-Forwarded-Proto changes as detailed in troubleshooting documentation). Because of the restart: always directive in docker-compose.yml, I expected harbor to automatically start up after rebooting. After restarting the docker daemon (or rebooting the system), not all harbor containers get started successfully.