-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Unable to load root folders #228
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
You're likely exec'ing into the container as root, but radarr runs as user |
Yes and that Here is how I am mounting the cifs share: |
I am having same exact issue. everything still works, adding new movies, importing from download client, literally everything besides seeing root folders and importing movies manually, ive tried downgrading versions the past few weeks, and still the same. I can delete movies still from the ui. I only set up this VM about 6 weeks ago and everything was fine then. I guess i havent tried to manually import since then so I'm not sure when it started. My fstab for mounting: I am getting the same exact error message as well. Docker version 26.0.1, build d260a54 EDIT: Updated to Ubuntu 24 with docker version 26.1.0 and its fixd |
I have also encountered this issue. Updating to Ubuntu 24 and docker 26.1.0 like mentioned by Mafyuh above, did not work for me. The only way I managed to get this to work was to set both PUID and PGID to 0. |
That means you have permissions issues, which you're bypassing by having radarr run as root, which we neither recommend, or support. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I am getting a similar error, except trying to add a root folder says it has invalid permissions.
When I try adding a root folder:
Yet, /data/media/movies has the following permissions:
The
The container sees the permissions as such:
Which if So I'm unsure what to do... |
I'm running into the same issue. abc user has 1000 as PID and GID and I confirm the directory has the same permissions from within the container but abc is unable to write to the directory.
|
Assuming this is a USB drive, it's mounted as root, the device needs to be mounted and the folders need to be owned by the uid/gid you're using. |
I was able to resolve the issue on my end by changing the docker container's directory mapping to /data/media instead of /media. I think since /media is already a directory in Linux this may have been causing issues with the mount. Once changed, the /data directory is owned by root but the subdirectories are owned by user abc and thus I can write/read to those directories. The mounted media is an nvme disk drive on the host machine just fyi. So two ways to solve this, either change the mount directory within the docker container or A third alternative might be to create your own image based off the radarr image where you can do the chown command there so it's automated but I would say just change the mounting directory on the container. |
Nevermind, I thought that solution worked but it didn't. I still have to chown the directory for it to work |
Last update, I think the issue is that within docker compose the abc user will only have access to the mounted directory NOT the entire path to the mounted directory. I had to change my volumes like so
Doing this lets user abc access the /data/media root directory for the general media setup settings and then I can add the movies and tv directory under the libraries section of radarr. This seems to work for me. |
It just sounds like your ownership of the folders isn't setup correctly if you're needing to chown. |
Is there an existing issue for this?
Current Behavior
I can see all my movies INSIDE the container.
I can also
write
to the/movies
folder from INSIDE the container.But I am unable to import my existing movies.
I have been using the same movies folder for few years without any issues.
This is what I see:
and this is the error I see when try and import:
Expected Behavior
Being able to import my existing movies.
Steps To Reproduce
Just spin up the docker and portainer.
Then setup using docker compose
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: