Ok I have a project that I’m currently running in 2 places as I learn how to use this system. The project is currently live on the internet and I’m taking it over. So I’ve got the project running on a desktop server and on Desktop for Windows as I go throughthe docker learning curves.
I’ve never used docker before a month ago. After 2 weeks of run around and trying to get a former employee to remember how the project works and all of the dependencies and then finding out that the code left behind was in a non-working state I have finally gotten the project to build and all of the associated images in the docker compose to run without exiting/erroring out.
As I said I have it running on an Ubuntu 22.04 server, and Docker Desktop for Windows. In both cases I’m getting 502 bad gateway. If I look at the logs of proxy(nginx) I see the following when trying to connect:
2023/08/01 20:10:37 [error] 7#7: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 172.22.0.1, server: 192.168.67.63, request: "GET /favicon.ico HTTP/1.1", upstream: "http://172.22.0.4:3005/favicon.ico", host: "192.168.67.63", referrer: "https://192.168.67.63/"
In addition to that my docker0 interface says it is DOWN even when my docker containers/images are running:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:15:5d:f5:98:4d brd ff:ff:ff:ff:ff:ff inet 192.168.67.63/20 brd 192.168.79.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::215:5dff:fef5:984d/64 scope link valid_lft forever preferred_lft forever 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:4d:1f:e4:97 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever
Based on my understanding of ther 502 error message from nginx it seems the link between eth0 and docker0 is broken or possibly because docker0 is “DOWN” then no traffic is passing between the two.
Is this a fair interpretation? If so, how can I fix this? If not, what other ideas are out there?
Thanks in advance.