4 days.
4 days?
4 days!
We made it 4 days before something else went wrong (I think thats got to be a new record for shortest time between major site issues). It turns out that we had two more issues with my docker setup of wordpress!
Issue 1:
So it turns out that when Watchtower updates my Docker containers, it sometimes does not reassign the volumes correctly. Those with a good memory may remember that this is EXACTLY what caused the first major issue, I just apparently never fixed it. When I get some free time in the coming months, I will sort out the root problem, but for now I have just disabled automatic updates on the wordpress containers…
Issue 2:
I use SWAG for reverse proxying on my server, (If you dont know what SWAG or a reverse proxy is, see my upcoming tutorial on how and why to use it over the alternatives) which allows me to get https and ssl encryption so that sites like this actually work on the public side. For SWAG to function properly, it needs to be able to communicate over the local network with the machines doing the hosting. So to get this working with Docker, I use a Docker network called “proxynet” (definitely not borrowed from this great tutorial). The only problem is, if the Docker container is unable to join this network, we get 502 errors up the wazoo as it cannot connect to the endpoint on the hosting server. Now in normal circumstances this shouldnt happen, unless, well, you have a Docker stack that does not specify to connect to the proxynet…. A quick read on the Docker compose docs and some testing later I managed to get my WordPress containers on the WordPress and the proxy network, and now it should never happen again :).
Anyways, just a small update. Things should be stable now, and when I get some more free time, expect some cool blog posts!