Closed acaranta closed 8 years ago
Corrections made according to your comments.
Awesome. Thanks a lot! I'm assuming you've tested it after the changes?
No indeed .... :p put that on hold for the moment ... (it was way too nice... it went too well ;) )
Well OK, I should have tested ....
However, the networking and DNS resolution is very weird, fails etc ... from what I see it should not be related to my setup... as i works 100% with my ubuntu version ...
alpine linux seems to handle DNS related queries differently ...
OK found the problem ... seems alpine does not use the resolv.conf like as usually ... if you have several nameserver statements .. they are not used in the 'correct' order ... therefore it can brilliantly fail if you have like me :
nameserver <internal IP1>
nameserver <internal IP2>
nameserver 8.8.8.8
In the current case, it searched against mainly google DNS .... which can not resolve my internal zones .... :/
Therefore, this can be an issue ... I'd say it's up to you to acknowledge if this is acceptable or not ... It is a problem with alpine, not our implementation anyway ;)
Yes, there are some differences in the way the libc in Alpine Linux does DNS resolution. Here's the explanation: http://www.openwall.com/lists/musl/2015/09/15/2. That being said, your image is fine as-is for me. Would you mind squashing your commits together before I merge? Thanks!
Done ;)
As it was suggested in #163 here is my solution in the form of a Dockerfile and a bit of help added to the Readme file.
FYI, this maestro-ng container is used in our company since well ... around a year and a half. It work for us, therefore I thought I could share ;)
Can be tried live from : https://hub.docker.com/r/acaranta/dockmaestro/