Boulder: Unable to setup SA gRPC server

[bmw]

I've been doing some testing with test/config-next to test with the "ready" status enabled and am repeatedly seeing boulder fail to start with logs like:

netaccess_1  | I204722 boulder-sa Versions: boulder-sa=(Unspecified Unspecified) Golang=(go1.10.2) BuildHost=(Unspecified)
netaccess_1  | E204722 boulder-sa [AUDIT] Unable to setup SA gRPC server: listen tcp: lookup sa1.boulder on 127.0.0.11:53: no such host
netaccess_1  | 
netaccess_1  | 
netaccess_1  | These processes exited early (check above for their output):
netaccess_1  |  'exec ./bin/boulder-sa --config test/config/sa.json --addr sa1.boulder:9095 --debug-addr :8003' with pid 875 exited 1
netaccess_1  | Unable to setup SA gRPC server: listen tcp: lookup sa1.boulder on 127.0.0.11:53: no such hostboulder_netaccess_1 exited with code 1

I was testing on 2dadd5e09a8228342aa86e8fa4c8d887a82aa4ac and the only changes to docker-compose.yml was setting FAKE_DNS to 10.77.77.1 and BOULDER_CONFIG_DIR to test/config-next.

Any ideas?

[rolandshoemaker]

Are you using --use-aliases?

[jsha]

You probably need to run docker-compose up boulder instead of docker-compose up. We recently added the netaccess container which, for complicated reasons, tries to compete with boulder and grabs its ports. We want to find a fix but haven't found one so far.

[bmw]

Are you using --use-aliases?

No. We've just been using docker-compose up -d, sometimes with the added boulder argument depending on the script.

You probably need to run docker-compose up boulder instead of docker-compose up.

That seems to have worked. I reran the script that was failing spuriously for me yesterday a few times and it always passed. I completely you forgot about you doing this in https://github.com/certbot/certbot/pull/6031.

Thanks for the help! Feel free to close this issue if you want.