Hi i have a error to sudo

[manolo_9045]

the problem its that it ask for a password that i dont have sudo apt install python3-torchvision
[sudo] password for worckbench:
Please describe your issue or request: (tick the boxes after creating this topic):

Please tick the appropriate box to help us categorize your post
Bug or Error
Feature Request
Documentation Issue
Other

[twhitehouse]

are you on a windows machine? it sounds like you are trying to install something in the WSL distribution.

if you want to install something in the project container you should use the environment configuration files or the package widget.

See docs here Environment Configuration - NVIDIA Docs and here Packages - NVIDIA Docs

[twhitehouse]

did this fix the issue?

[manolo_9045]

thanks, i use root to solve the problem. but i think that also works thanks.

[davemaster99]

Greetings,

How about SHARE the sudo password; come on, I will give it to NOBODY

thanks in advance…

[twhitehouse]

Hi Dave,

Thank you for raising this.

We have sudo blocked in the running container for a variety of reasons.

However, you raise very good point about doing things interactively. It is a bit klunky to force everything into the scripting setup.

Let us have a think and get back to you on this.

In the meantime, you should be able to do everything you want using sudo in the preBuild and postBuild scripts. You can also add packages and such through the environment manager.

[davemaster99]

@manolo_9045

sudo

Can the folder “Project” reach from postbuild,bash? Path? Thanks in advance

[twhitehouse]

The build scripts are in the Project root, everything should be relative to that.

[davemaster99]

Greetings,

But, when I tried to have access to files into the /project/ folder, I got an error message: file does not exist

[edwli]

I think I understand what you are trying to accomplish now. The creation of the /project location happens after the postBuild.bash script is run. And so you are unable to access the /project container location inside the postBuild.bash script. In that case, I would try to use a different location, if possible.

The reasoning behind this is we want a clear separation between the container build process and the container run process. The build should affect the container itself whereas when we run the container we expose a certain level of access to the user where /project is the root level.