Computing on Demand PC News & Reviews
For those of us that are fans of TrueNAS Scale and look to leverage the platform for its capabilities beyond file storage, there is built-in functionality to run VMs and Containers. If you are here reading this, my assumption is that you already know this and experienced the same issue I did when installing the Nginx reverse proxy “Container Startup Probe Failed”.
For me, installing the reverse proxy on one of our client’s systems kept prompting us with an error no matter what we tried, “Container Startup Probe Failed.” I upgraded the system OS, built a test system to replicate the issue, racked my brain, then discovered I wasn’t alone. One of the things that led to our somewhat obscure circumstance is that our customer’s system is built completely with spinning disks, except for the OS (budget constraints).
This type of configuration actually led to timeouts when trying to load from the slower spinning disks, prompting us with the dreaded message. To alleviate this, simply add an ENV variable to the configuration for the reverse proxy and all your problems will melt like jelly beans on a driveway in June.
S6_STAGE2_HOOK=sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
Description of the fix given by Daniel Siquara: “This will remove the last line that was added in version 2.10+ chown -R “$PUID:$PGID” /opt/certbot with takes a long time on HDD pools”
Enjoy!
