Skip to content
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

Closed
poldim opened this issue Oct 13, 2021 · 6 comments
Closed

Permissions issue causing a boot loop #694

poldim opened this issue Oct 13, 2021 · 6 comments
Labels

Comments

@poldim
Copy link

poldim commented Oct 13, 2021

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

==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
==> Performing startup jobs and maintenance tasks
chown: changing ownership of '/app/data': Operation not permitted
@poldim poldim added the help label Oct 13, 2021
@louislam
Copy link
Owner

Uptime Kuma is not working on NFS, as it is using SQLite. Please change to a local volume.

@PopcornPanda
Copy link
Contributor

You could do dangerous workaround this and export nfs volume with no_root_squash option.
But be aware, that's not recommended.

Another way is running container as normal user, not root. Maybe podman would be suitable for this.

@nbvcxz
Copy link

nbvcxz commented Oct 16, 2021

I guess no_root_squash if only dirty hack for now. I'll try to make a patch during the weekend (testing is the longest part) to exclude files_ownership procedure when on NFS (if it's possible).

@louislam
Copy link
Owner

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

@poldim
Copy link
Author

poldim commented Oct 16, 2021

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?

@louislam
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants