Docker: Use hostname instead of IP addresses about pebble HOT 7 CLOSED

There is PR with the fix: letsencrypt/challtestsrv#20

from pebble.

from pebble.

OK, let's make a short story long. 😉 I'm running integration tests in Java, and I'm starting the docker containers from the build script.

I have used a construct like this, where getent hosts resolved the IP from /etc/hosts:

  <arg>sh</arg>
  <arg>-c</arg>
  <arg>pebble -strict -dnsserver $(getent hosts challtestsrv|cut -d' ' -f1):8053 -config /test/config/pebble-config.json</arg>

Unfortunately it won't work anymore, because the new pebble and challtestsrv images are based on the scratch image, so there are no commands like getent, or even cut.

Then I tried to set up a network with fixed IP addresses, like in Pebble's docker-compose.yml. But the docker extension of my build tool is unable to set up networks, neither in the build script nor by using docker compose. I would have to set up the network manually before running the integration tests.

My current solution is to build fresh docker images based on alpine, and "steal" the relevant application files from the new pebble and challtestsrv docker images. Now I can do my getent hosts challtestsrv trick again. (Well, it works, but it won't win a beauty pageant.)

In my example above, it would be unnecessary to set up a subnet with fixed IP addresses, and I also wouldn't need the getent trick.

from pebble.

We should be able to support hostnames instead of hardcoded IPs, and I think that makes sense to do. I'll take a bit of a run at it.

from pebble.

Duplicate of #418?

from pebble.

Thanks @mitar, I didn't notice that PR (sorry, I wasn't watching the challtestsrv github repo). Yes, I do think that's a duplicate, and we can use your work there.

from pebble.

On Pebble's side, the -dnsserver option already seems to accept hostnames. So @mitar's PR would resolve this issue.

I'm closing it as duplicate. Thank you!

from pebble.