Explanation on the last commit: there was something set that apparently got overwritten / reverted when I rebooted the server earlier this morning. After that the container was unable to write to /opt/caddy and refused to start. The reason for this is that docker on Ubuntu runs as a snap by default. Snaps can't write outside $HOME without special configuration. The auto-deploy.yml has been changed so that caddys config files and persistent storage is now within the users $HOME. Next commit will update the auto-deploy-prod.yml too.
Usually there should be another PR and issue for all of this but since it got discovered setting up the key based authentication I might as well fix it in here too.
jondef
commented
1 year ago
Explanation on the last commit: there was something set that apparently got overwritten / reverted when I rebooted the server earlier this morning. After that the container was unable to write to /opt/caddy and refused to start. The reason for this is that docker on Ubuntu runs as a snap by default. Snaps can't write outside $HOME without special configuration. The auto-deploy.yml has been changed so that caddys config files and persistent storage is now within the users $HOME. Next commit will update the auto-deploy-prod.yml too.
Usually there should be another PR and issue for all of this but since it got discovered setting up the key based authentication I might as well fix it in here too.