wdcew Posted April 10, 2021 Share Posted April 10, 2021 I just upgraded from 6.8 to 6.9, and the Docker page didn’t display properly, and when I went back to 6.8, the Docker page did. I found that the Docker was already running on Linux, and I was able to run the various containers from the command line, and the Docker log file didn’t show any errors. How to deal with such a situation? tower-diagnostics-20210410-1254.zip Quote Link to comment
ChatNoir Posted April 10, 2021 Share Posted April 10, 2021 This might be linked to your issue ? This error is all over the place Apr 10 12:53:40 Tower nginx: 2021/04/10 12:53:40 [crit] 7054#7054: *1203 connect() to unix:/var/tmp/code-server.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.31.199, server: , request: "GET /dockerterminal/code-server/ws HTTP/1.1", upstream: "http://unix:/var/tmp/code-server.sock:/ws", host: "192.168.31.225" With this Apr 10 12:50:56 Tower dhcpcd[1709]: br0: Router Advertisement from %redactedIPV6 I also see this Apr 10 12:48:06 Tower rc.docker: invalid CIDR address: %redacted IPV6 that looks incomplete/72 Quote Link to comment
wdcew Posted April 10, 2021 Author Share Posted April 10, 2021 5 minutes ago, ChatNoir said: This might be linked to your issue ? This error is all over the place Apr 10 12:53:40 Tower nginx: 2021/04/10 12:53:40 [crit] 7054#7054: *1203 connect() to unix:/var/tmp/code-server.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.31.199, server: , request: "GET /dockerterminal/code-server/ws HTTP/1.1", upstream: "http://unix:/var/tmp/code-server.sock:/ws", host: "192.168.31.225" With this Apr 10 12:50:56 Tower dhcpcd[1709]: br0: Router Advertisement from %redactedIPV6 I also see this Apr 10 12:48:06 Tower rc.docker: invalid CIDR address: %redacted IPV6 that looks incomplete/72 Yes, it is my network problem. I solved it by using the proxy and the docker page is now displayed normally 1 Quote Link to comment
ChatNoir Posted April 10, 2021 Share Posted April 10, 2021 1 minute ago, wdcew said: Yes, it is my network problem. I solved it by using the proxy and the docker page is now displayed normally Good news. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.