Closed juanmatias closed 1 year ago
Adding a possible scenario we found with @diego-ojeda-binbash and @rodriguez-matias in which the image is used to run a container inside an Ubuntu based self-hosted runner but it can not resolv hosts from inside it. Notes: while Alpine base does not work, Debian based does.
Possible root cause: musl DNS library issue with using only UDP and not UDP/TCP.
Solution proposed by musl matainer is using a custom DNS resolver. So maybe switching bases is the key here.
It is done and ready to merge. PR https://github.com/binbashar/le-docker-leverage-toolbox/pull/33
This PR will close https://github.com/binbashar/le-docker-leverage-toolbox/issues/39 as well.
Describe the Enhancement
Switch the docker base image from Alpine to Debian.
Expected Behavior
Debian ecosystem should be available.
Use Case
Currently, the Alpine base image is being used. It is well know the issue with C libs. Same as this one, other problems arise from using this base image. To avoid having to hack the image in order to put it to work, using the Debian base image will provide the needed ecosystem.
Describe Ideal Solution
Replace Alpine with Debian.
Alternatives Considered
Keep hacking the container image build in order to keep it working.
Additional Context
n/a