Timeline for DNS resolution fails when container is started via docker-compose
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 27, 2021 at 14:17 | comment | added | AdrianDeWinter | yep. I would love to find out why this workaround is even necessary, aka why does the linux container get proper DNS responses with the default network, but not the windows container? Anyways, it seems like i wont get an answer to that anytime soon. I'll add the Workaround as an awnser, for anyone else who stumbles across this problem | |
| Oct 26, 2021 at 14:05 | comment | added | mikequentel | @AdrianDeWinter looks like you solved it--the dns block in docker-compose.yml | |
| Oct 25, 2021 at 22:46 | comment | added | AdrianDeWinter | Thanks for the suggestion, unfortunately it did not work. I didn't expect it to, though, since the server starts up properly (and reads the mounted files without issue). The problems start when clients attempt to connect to it. Some further testing has revealed that something is wrong with the containers name resolution when it is started via docker compose. I have updated the question with further info | |
| Oct 25, 2021 at 15:39 | history | answered | mikequentel | CC BY-SA 4.0 |