Troubleshooting
Fix config-file permission and bind-mount errors for portunus-standalone.
Common failures
- Config-file permissions matter.
- systemd: the process runs as
User=portunuswithReadOnlyPaths=/etc/portunus. The installer setschown root:portunus+chmod 0640. Anything stricter (e.g.chmod 0600 root:root) will cause startup to fail. - Docker: the container runs as UID 65532. The host file must be
readable by that UID —
chmod 0644is the simplest fix.
- systemd: the process runs as
- Snap-packaged Docker on Ubuntu confines bind-mount sources to
/home,/media,/mnt, and a few other allowlisted paths. Bind-mounts from/root,/tmp, or/etcwill surface asNo such file or directoryinside the container. Keepportunus.tomlunder/home, or install the non-snapdocker-ce/docker.iopackages.