-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permissions issue causing a boot loop #694
Comments
Uptime Kuma is not working on NFS, as it is using SQLite. Please change to a local volume. |
You could do dangerous workaround this and export nfs volume with no_root_squash option. Another way is running container as normal user, not root. Maybe podman would be suitable for this. |
I guess |
SQlite won't be working on NFS, even though you pass the chown problems. I also mentioned that in the Readme (https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install). Related issue: #127 |
Is there a way to split the location of the configuration so it could be stored remotely on NFS while still using local storage for the database? |
Backup approach such as rsync. |
Describe your problem
When starting uptime-kuma, it fails to change ownership of the data files (entrypoint.sh).
I run a docker host that writes to volumes accessed over NFS on a NAS. The docker host has read & write access to the folders mounted within the volumes. Containers from this docker host can write data on the shared volume, create folders, etc, but cannot change ownership permissions. This solution works great for many containers and I haven't seen a similar issue to this.
Info
Uptime Kuma Version: latest
Using Docker?: Yes
Docker Version: Docker version 20.10.9, build c2ea9bc
OS: Ubuntu
The text was updated successfully, but these errors were encountered: