Open AlexanderZhirov opened 2 years ago
UPD. I have reassembled the assembly with the ability to debug (/usr/bin/dockerd --debug -H fd://
). I attach the FULL docker download docker.log.
I have extracted the log BEFORE and AFTER restarting docker.socket
. I share a comparison of two logs. As you can see, after restarting docker.socket
adds new rules via iptables
.
I'm getting a similar issue. In my case the container runs well but if I reboot my VM my container is show by docker ps
and the logs show that is alright but when I tried to access on browsers it's fails.
I can only resolve restarting my container.
I made an assembly based on Thinstation. Added package
docker
. I run the distribution, everything loads without problems. Docker starts after downloading the distribution. I downloadnginx:alpine
and run it with port80
forwarding. The container starts, there are no problems:Rules table:
The problem is that I can't connect even locally to the lifted container at the
localhost
address.Telnet
also does not connect to port80
. The remote connection doesn't work either.If I restart
docker.socket
- access to the container from the outside is provided, I open the page in the browser.My question is this: how to understand and why the initial launch of Docker after downloading the distribution does not provide access to running containers? Why does it start working only after restarting
docker.socket
?I also attach the full distribution download log and the Docker startup log.
docker.gz load.gz
I also provide an infographic of the distribution download: