I just performed a first, fresh central install following the clear documentation page
The server seems to be ok but docker-compose ps returns an exit0 status for the "secrets" container.
root@scw-central:~/central# docker-compose ps
Name Command State Ports
---------------------------------------------------------------------------------------------------------------
central_postgres_1 docker-entrypoint.sh postgres Up 5432/tcp
enketo docker-entrypoint.sh /bin/ ... Up 8005/tcp
enketo_redis_cache docker-entrypoint.sh redis ... Up 6379/tcp
enketo_redis_main docker-entrypoint.sh redis ... Up 6379/tcp
mail /bin/entrypoint.sh exim -b ... Up 25/tcp
nginx /bin/bash /scripts/odk-set ... Up (unhealthy) 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
pyxform waitress-serve --port=80 - ... Up
secrets docker-entrypoint.sh ./gen ... Exit 0
service docker-entrypoint.sh ./wai ... Up 8383/tcp
I think this is the expected behavior but @issa will need to confirm. It's what I see on my servers as well.
The secrets container is used generate an API key and encryption keys to pass on for the Enketo build. It runs a script and then is no longer needed. There's no ongoing foreground process so its status is Exit 0.
What happens when you try to access your servers, @Morck, @AlexCF?
@mathieubossaert were you always able to access yours? The more troubling part about your initial ps output was the unhealthy state for nginx but I don't think you asked about that. Either way, @issa's suggestion seemed to resolve it which is good.