nginx-frontweb: nginx-frontweb crash-loops after auto-update, rolled back Friday 24th July 2026 22:23:50

(advisory — machine-generated by hermes3:8b, ~664 tokens; not verified. This is the LLM's own note; the operator writes their own write-up separately.)

What happened: The nginx-frontweb service experienced a crash-loop following an automatic update. The update pulled in the latest upstream CI build of the docker-gen container, which included changes to the docker-entrypoint.sh script. This new version of the entrypoint script ran 'command -v' on our flag-style command under set -eu, causing the probe to return non-zero and aborting the container before its fallback. Consequently, the health check failed, triggering a rollback to the previous images.

How it was resolved: The self-hosted compose-orchestration cluster automatically rolled back to the previous image version after the post-update health check failed.

Prevention:

1. Pin the docker-gen image tag to a specific release in the compose YAML files to avoid pulling unstable CI builds.
2. Increase the health-check timeout for the nginx-frontweb service to allow additional time for any potential issues with the new update to be resolved before marking it as healthy.
3. Review and test any upstream changes from the docker-gen repository PR #761, such as the modifications made to the docker-entrypoint.sh script, in a staging environment prior to deploying them to production.