R
Runpod•3mo ago
オオガミ

No root on pod. Cannot write to workspace.

I've tried launching a new pod, but same error. It was working perfectly fine yesterday, so I'm not sure what's happening or if I should make a support ticket for this. I've tried 
(f2l) mambauser@3ccffae5dc96:/$ chmod -R 775 /workspace/
chmod: changing permissions of '/workspace/': Operation not permitted
(f2l) mambauser@3ccffae5dc96:/$ chmod -R 775 /workspace/
chmod: changing permissions of '/workspace/': Operation not permitted
(f2l) mambauser@3ccffae5dc96:/$ login
login: Cannot possibly work without effective root
(f2l) mambauser@3ccffae5dc96:/$ login
login: Cannot possibly work without effective root
echo "test" > /workspace/test_file.txt
bash: /workspace/test_file.txt: Permission denied
echo "test" > /workspace/test_file.txt
bash: /workspace/test_file.txt: Permission denied
I realized it after trying to use my gdown script and getting a permissions error 
Downloading data from Google Drive... This may take a while.
Error:

        [Errno 13] Permission denied:
        '/workspace/data_bundle.ziplw0vwio5.part'
Downloading data from Google Drive... This may take a while.
Error:

        [Errno 13] Permission denied:
        '/workspace/data_bundle.ziplw0vwio5.part'
Thank you in advance for any advice. PodID: 0e4vzkyp28xt15
6 Replies
Dj
Dj•3mo ago
/workspace is technically not your directory to edit unfortunately (it belongs to the host) but you should still have the ability to write to it so long as it's mounted?
Dj
Dj•3mo ago
Does your started pod look like this with a Volume explicitly named?
No description
オオガミ
オオガミOP•3mo ago
Yes, it's explicitly listed as /workspace in my dashboard
No description
オオガミ
オオガミOP•3mo ago
There should also still be files in /workspace/ from the other day, but when I ls workspace, it returns empty, so potentially I can't even read it? Though, I assumed the files were just deleted (which is a nonissue if so).
Henky!!
Henky!!•3mo ago
Try https://henk.tech/ccnperunpod as the template Mine also installs mamba (and packages you can specify yourself) and should use root to avoid this kinda stuff mambauser isnt a good default but common
オオガミ
オオガミOP•3mo ago
It turned out to be a mambauser permissions problem as you said. I'm not sure why all the sudden it stopped wokring but I think it was due to me trying a no-cache build when there was a mirror sync on nvidia's servers. I revised my dockerfile to set the correct permissions and it's fine now. Thanks.

Did you find this page helpful?