# Root privileges **URL:** \ **Category:** Spaces\ **Created:** [September 18, 2024, 9:11am UTC](https://discuss.huggingface.co/t/root-privileges/107179 "2024-09-18T09:11:29Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 18, 2024, 9:11am UTC](https://discuss.huggingface.co/t/root-privileges/107179/1 "2024-09-18T09:11:30Z")
Hello community, i have a problem, the docker itself have root permission but the running script doesn’t. Why? ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [September 18, 2024, 10:39am UTC](https://discuss.huggingface.co/t/root-privileges/107179/2 "2024-09-18T10:39:23Z")
Is this a case of not being able to access the Python folder during installation, something I’ve seen Docker users lament on the forums? The environment variable dedicated to it didn’t seem to work as expected either. Maybe that was a bug. If that’s the case, I’ll have to scour the logs a bit… ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 8:41am UTC](https://discuss.huggingface.co/t/root-privileges/107179/3 "2024-09-19T08:41:34Z")
Yeah, the python script running in container can’t use apt and sudo ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 8:45am UTC](https://discuss.huggingface.co/t/root-privileges/107179/4 "2024-09-19T08:45:14Z")
```auto ===== Application Startup at 2024-09-19 08:44:23 ===== sudo: The "no new privileges" flag is set, which prevents sudo from running as root. sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag. ``` ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [September 19, 2024, 8:54am UTC](https://discuss.huggingface.co/t/root-privileges/107179/5 "2024-09-19T08:54:55Z")
Anyway, I brought the logs. It was not resolved in the end at that time. > [@Environment Variable in build time](https://discuss.huggingface.co/t/environment-variable-in-build-time/104436/4): > > Is that just a bug…? Basically, there are quite a few features that aren’t used very often that are buggy. No one reports it, so none of the developers notice… I don’t know where to report bugs in Spaces. HF doesn’t have a DM, so the only way is to send a mentions to someone who seems to have admin rights, or hit up Discord, or open a Discussion with a randomly selected HF staff repo. P.S. By the way, what I would do is either find another alternative tool because I’m too lazy to wait, or c… In addition to requirements.txt, there are pre-requiements.txt, packages.txt and README.md that can be used during installation in the HF VM, and maybe other magic word-like files. Also, there are a lot of hidden functions in the environment variables. I’m hoping you can give me some clues. ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 9:08am UTC](https://discuss.huggingface.co/t/root-privileges/107179/6 "2024-09-19T09:08:08Z")
I searched a lot but nothing found, the solution is passing a docker flag, which is not possible without cli ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [September 19, 2024, 9:15am UTC](https://discuss.huggingface.co/t/root-privileges/107179/7 "2024-09-19T09:15:57Z")
I’ve just lightly searched the forums too, but I can’t find any satisfactory answers, even though various people have asked questions… A bug or a bad spec is, well, the same thing, but what’s this? I don’t think HF will support Docker itself if the only way to do that is to deploy just the contents of the Docker container again… Should we send a mentions to HF staff? @+username I’m from a time before Docker came out, so I still don’t know much about Docker. If we could put it in the form of ‘it’s weird that this command or environment variable doesn’t work’, it would be easier to communicate, but can you summarise that succinctly? ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 9:28am UTC](https://discuss.huggingface.co/t/root-privileges/107179/8 "2024-09-19T09:28:45Z")
Used RUN instead of CMD for running python script, But, do you know how long it takes for space to turn off? ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 9:30am UTC](https://discuss.huggingface.co/t/root-privileges/107179/9 "2024-09-19T09:30:22Z")
> [@John6666](#): > > Should we send a mentions to HF staff? @+username They know better ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [September 19, 2024, 9:31am UTC](https://discuss.huggingface.co/t/root-privileges/107179/10 "2024-09-19T09:31:43Z")
You mean the specifications! It depends on what you mean **turn off** , but the timeout for the start-up process itself is 30 minutes. ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 9:34am UTC](https://discuss.huggingface.co/t/root-privileges/107179/11 "2024-09-19T09:34:18Z")
Yeah, so thats not the solution. Hope a HF staff see this ---
**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\ **Post date:** [September 19, 2024, 9:37am UTC](https://discuss.huggingface.co/t/root-privileges/107179/12 "2024-09-19T09:37:57Z")
No, I don’t think staff see the forum nearly as much as they do. They’re often unaware of the complaints and glitches that you can see if you look at the forums. It’s not that weird though, because they are staff, but their profession is not forum watchers. It’s customary to call them up with a mentions when you have a problem. You need someone who knows who to send it to to do it… but I probably don’t even know 10% of them. > **[@victor on Hugging Face: "🙋 Calling all Hugging Face users! We want to hear...](https://huggingface.co/posts/victor/964839563451127)** > > We’re on a journey to advance and democratize artificial intelligence through open source and open science. P.S. Incidentally, I don’t have a Discord account, but a forum mate told me that when he complained on the HF Discord, he got an immediate response. ---
**Author:** ![mmty](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@mmty](https://discuss.huggingface.co/u/mmty)\ **Post date:** [September 19, 2024, 9:39am UTC](https://discuss.huggingface.co/t/root-privileges/107179/13 "2024-09-19T09:39:39Z")
Ok, thanks