Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Permissions issue causing a boot loop

See original GitHub issue

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