Closed beltet closed 1 year ago
Seems like the Ubuntu container have network, so the problem is isolated to this container...
Did you attempt to try network_mode: host
for diagnostic purposes?
Cause if that works it means your host config/ipfirewall/etc is FUBAR and beyond the help of this issue tracker.
Did you attempt to try
network_mode: host
for diagnostic purposes?Cause if that works it means your host config/ipfirewall/etc is FUBAR and beyond the help of this issue tracker.
Ok. I have now tested it, and I cant get any connection either. Will try to poke the firewall on the host and on my network and see if the problem is there.
EDIT: I've used network: host and changed the resolv.conf to include cloudflare & Google DNS. Then it works. But when I remove the network: host I can't connect any more. Will investigate and report.
EDIT2: I've tried removing "network: host" from the compose file and then it fails, I have system pruned everything so that shouldn't be any dangling containers that can interfere.
I've also tried adding nameservers in /etc/network/interfaces but to no avail.
The only thing that solves this is changing /etc/resolv.conf and making it immutable with chattr +i /etc/resolv.conf
and also add network: "host"
in docker compose file
This is outside the scope of this issue tracker.
It is assumed you have a functional network stack, correctly set up docker ect before starting.
Null and void issue.
Hi! I cant seem to get the container working. Been at it for quite a while now...
The container just keeps rebooting. And don't ever start the server application.
Here is the docker-compose(the ubuntu container is only there to test network inside of docker network).:
Here is the log output: