Just tried to browse to one of my services that caddy is handling, and found the page refused to load. Logged into the server and saw that caddy container has stopped 8 hours before that, checked the logs and I’ll attach them below
haven’t tried anything yet since this is the first time this has happened. I recently updated the docker container for caddy, so that might be related. but I was hoping someone could shed some light on the log messages as to why it shut down.
Don’t use that image. That’s not the official Docker image for Caddy, that’s our CI target. The official image is caddy, not caddy/caddy. See the docs Docker
Follow those docs to make sure you’re using the latest version and the right volume mappings.
As for Caddy shutting down, it was sent a SIGTERM signal. Did you run package updates that updated Docker? If Docker itself is updating, it first shuts down all the containers since it needs to reboot the Docker daemon afterwards. You should set a restart policy on your Caddy container so it comes back online after doing so.
Yeah, that guide is also outdated since it pulls the bitwarden_rs docker and not the vaultwarden one. I opened a ticket to Linode to open up their guides to edits or suggestions to avoid this in the future.
Anyway, thanks, I updated to caddy instead of the CI image, and also changed the restart. have a great day!
Their guides are on github, in that repo I linked. Users can propose pull requests to fix them. But all the Caddy guides are outdated in various ways. I’d rather people just use our official documentation, which is kept up to date.