Cannot get homarr v1.0.0-beta4 to start (permissions)
I have been unable to get appropriate permissions set up for /appdata. Tried setting perms to 777, subdirectories are created but container is unable to chown. Recently tried just using a volume instead of a bind and now getting
mkdir: can't create directory '/appdata/db': Permission denied Is there a way to set the uid/gid that the container runs as? Passing them as env vars did not appear to work14 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Can you send your compose file?
I had this issue too. After folder created i checked the permissions and it was read / write I add execute and it’s fix the problem
Didn't use compose, just built it in portainer but here's the config inspection there with RW on the volume mounted to /appdata
I've tried adding 777 to the db and redis folders it creates, but it still desperately wants to chown the folders and won't start unless its able to
Did you use -r?
sudo chmod -R 777 /homarr
You need to run this command only on homarr folder
-r stands for recursive so it applies to everything inside and not just the folder.
you can do
ls -lhs to check the permissions, owner and groups of a file or directory.its able to create the directories, and these are what I see from the host, but its failing all the chown operations in the container and restarting
I don't know what the 1001 and 65533 user / groups are, I haven't set those and I'm unable to tell the container to use different uid/gid
1000 and 1001 are usually the first user made for the system.
65533 is the last group ID (there can't be a higher ID than this one).
It's not really important though if you end up doing a chmod -R 777 anyway
Here we can see your folders have 755 permissions, not 777. And I wouldn't be able to tell you for the nested files
With the parent folder set to 777, these are the permissions the container creates the folders with. There are no items in the folders, and recursively marking everything in the parent folder 777 results in the same error with the chown operation not being permitted. Identical behavior when using a docker volume vs a bind
Also, the owner being 1001 seems to mean you should already have the right owner.
Try to keep everything and just manually chown the folders and the contents.
sudo chown -R 1001:1001 /mnt/config/homarr-beta
Then do the same with sudo chmod -R 777 /mnt/config/homarr-betaokay, got a different error now
su-exec: setgroups(1001): Operation not permitted