Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pebble-challtestsrv: allow defaultIPv4 to be a hostname #418

Open
mitar opened this issue Nov 1, 2023 · 1 comment · May be fixed by letsencrypt/challtestsrv#20
Open

pebble-challtestsrv: allow defaultIPv4 to be a hostname #418

mitar opened this issue Nov 1, 2023 · 1 comment · May be fixed by letsencrypt/challtestsrv#20

Comments

@mitar
Copy link

mitar commented Nov 1, 2023

Currently one has to provide just an IP address for defaultIPv4. But when running inside CI you might not know the IP because it could be dynamic, but you do get a hostname: e.g., in Docker network setting a target container might get a hostname you can resolve to. Being able to provide that hostname directly instead of having to script resolving it first myself would simplify things a lot.

My context is GitLab CI where I can define a service but the command is a hard-coded string.

My current workaround is to provide an ash command-line script which resolves the IP and then calls pebble-challtestsrv, but it is ugly. (An alternative to put that into a script would instead require from me to build a custom Docker image.)

@mitar
Copy link
Author

mitar commented Nov 1, 2023

I made letsencrypt/challtestsrv#20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant