The first set of warnings you report are benign, those are just because the docker-compose environment spins up multiple containers simultaneously, and it takes a moment for them to establish connections to each other.
The second set of errors is because the database contains zero issued certificates. The crl-updater considers the situation where zero certificates exist to be so cosmically unlikely (given that we issue 7 million certificates every day) that it must be the result of an error.
Note that the environment you're running is not intended to be a production deployment environment. The docker-compose.yml file and all of the //test/config[-next]/service.json files are designed around the requirements of our integration test environment. We have wholly separate, unfortunately not open-source, infrastructure and configuration for our production environment.
At the end of the day, we are a very small team who develop Boulder (and its test environment) for our own purposes. I'm very happy to see you running Boulder for your own project, but we cannot provide extensive support or debugging for situations that fall outside our core use-case.