Errors when starting the docker container
Im not entirely sure what I am doing wrong when starting the container but I keep getting this error when I attempt to start the container
37 Replies
Hi @Phoenixx , the mounted icons directory is either read-only or the docker user does not have the correct permissions.
These are the permissions for the directory, what should they be set to?
Which user is running docker?
What is your compose?
The user is phoenixx and you want what is in my docker-compose file?
That is the contents of my docker-compose file
My issues are probably going to be with the permissions or this docker file since I have both a minecraft server and mealie running on docker on this same computer
Other containers shouldn't interfere, as long as you don't mess up ports or network config.
Looking at the compose file and you
ls
list, I'd say that docker isn't running as pheonixx
Are you sure that it is?It should have been running as phoenixx, how would I check this
I am semi new to docker, I have done some in the past including in my college's devops class but that itself was very minimal
Medium
Understanding how uid and gid work in Docker containers
Understanding how usernames, group names, user ids (uid) and group ids (gid) map between the processes running inside a container and the…
Please note that Homarr currenlty has a bug with UID and GID, where it might not work / start / migrate the db when they are specified.
I specified uid and gid in the docker compose file and it is still giving the same error, does that mean it the issue is now the bug or is there something else at play?
Providing a user can trigger the bug.
But if it's still the same error, I'd say that something else is interfeering
The new error is longer this time
Still the same reason though
You could test, whether it's a permission issue, by setting 777 on the file.
Just don't run it permanently this way, as the use of 777 is discouraged due to security.
Setting 777 on the docker-compose or app?
All the mounted directories - not the compose file
Alright
This is what perms look like now
Nope did not change
Other than going back to the previous error
Is
/home/phoenixx/Desktop/homarr/icons
read only?
If not, can you completely delete the container, directories and repull the image? (don't forget to back up files if you created any boards in Homarr).It seems like I can do stuff since I can use touch and create a file then edit the file with no issues and without sudo
Should I add --user uid:gid \ to the command?
This command
No
alright
Default permissions for the directories
Let them be owned by root for now 👍
Back to this error
What are the directory permissions now?
Can you remove the container again and start using
--user 0:0
or --user root:root
?Yeah
Thats with --user 0:0
No logs at all? Even after a few seconds?
Yeah
Then I don't know what we could try next. @ajnart @Meierschlumpf do you have an idea?
Im going to try root:root, maybe itll make a difference maybe not
Still the same issue
Not sure, but you seem to have two different directories that could be mounted. Can you check, that you changed the permissions to your phoenixx user for both? I'm not sure other than that what could be the issue
I fixed that issue, there is now one directory
Any other ideas in which I could try?
!NOT RECOMMENDED!
Chmod 777 all of them
If it still doesn't work then, it means it's not a permission issue, that's for certain
Will try chmod 777 when I get home
Yeah still having the same issue
@Phoenixx try removing the mount point for configs or use a volume instead
I figured out the issue, it had to do with SELinux
Can you post the solution here, so other users can use it as well?
@Phoenixx