Cannot set DNS server in Docker image about pebble HOT 10 OPEN

Thanks, those seen like issues we should correct.

from pebble.

EDIT: I'm sorry, I just realized this should rather be a new issue.

from pebble.

As a workaround, I was able to specify a custom DNS server for the entire Docker container, but this required changing the port to 53.

Is there anything specific you had to do to make this work? I've tried adding dns: under pebble in compose.yml, and appending -dns01 :53 to the pebble-challtestsrv command, but it doesn't seem to work.

from pebble.

As a workaround, I was able to specify a custom DNS server for the entire Docker container, but this required changing the port to 53.

Is there anything specific you had to do to make this work? I've tried adding dns: under pebble in compose.yml, and appending -dns01 :53 to the pebble-challtestsrv command, but it doesn't seem to work.

I have not tried pebble-challtestsrv as I am running a custom DNS server that listens on 172.17.0.1:53. Pebble is able to resolve domains when I start the container with --dns 172.17.0.1.

from pebble.

After further investigation, the issue seems to be that container parameters are being altogether. The following invocation should fail, but the invalid parameter goes unnoticed

This is a pebble bug, not a container one. Positional (non - flag arguments) are ignored by pebble and doesn't throw an error.

Providing a flag properly "fails":

 docker run ghcr.io/letsencrypt/pebble:2.5.1 -test
flag provided but not defined: -test

So it is not the source of -dnsserver not working for you

from pebble.

I can confirm. I spent two days debugging this now. :-( Docker image for pebble does not respect anymore CLI arguments. So it is not just -dnsserver, it ignores -config as well. Try running with -config /nonexistent and it will start. v2.3.1 does not start.

Furthermore, pebble-challtestsrv Docker image also ignores CLI arguments. E.g., -defaultIPv4 is ignored.

from pebble.