Permissions Issue When Mounting Volumes

[daya0576]

Summary

The root cause of the permission issue:

The old image started by default as root, so it was always able to write to any filesystem. With the new configuration, it starts by default as user nobody, which doesn't have any permissions on the user's filesystem.

Changes:

• change file permissions, start as nobody #18
• update readme for rootles image #22

Issues:

• Version 0.3.4 not saving input #21
• Unable to open database #23
• Permission issues for rootless container running with Podman #24
• Application startup failed when trying to run with docker #32

Solutions

Make sure the UID/GID of the user executing the main process in the container is the same as the owner of the folder/files on the host.

Option1:

Run Docker containers as the owner of the existing folder/files on the host

docker run -d --name beaverhabits \
  -u $(id -u):$(id -g) \
  -v /path/to/host/directory:/app/.user/ \
  ...

# In case the existing path is owned by root:
# chown -R $(id -u):$(id -g) /path/to/host/directory

Option2:

Update the owner of the folder/files on the host as nobody

$ sudo chown -R 65534 .user

Option3:

Run Docker containers as the default "root"

[daya0576]

Hi @SylivanKenobi I hope all is well. I did some research and created a wiki page for the Docker permission issue.

Could you please review it and provide any suggestions? Also, feel free to edit the page. Thank you.