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. |
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: