Hi Christopher,

The user is created to not run NEST inside the Docker image with root privileges. Additionally the user gets the user ID of the host system to allow a smooth exchange of files.

As far as I know, Singularity and Sarus make sure that the user inside the container is the same as the user outside the container. Everything should work with that as well.

For a first test on PizDaint I also simply skipped the creation of the user (even a bit more): https://github.com/steffengraber/nest-docker/blob/piz-daint/src/piz-daint/en...

Best

Steffen

Am 13.01.20 um 17:04 schrieb bignamini@cscs.ch:

Hi all,

I have a question about nest user creation/usage in nest docker entrypoint file: I am working with Sarus and Singularity and due to some permission limits I can't create a new user inside a container. I have tried to modify the entrypoint.sh file as follows

https://github.com/ChristopherBignamini/nest-docker/blob/no_nest_user_creati...

in order to skip the creation of the nest user. I am not a nest expert but everything seems to work, at least if I try to run a couple of examples like one_neuron.py and twoneurons.py.

My question is: what is the reason behind the creation and usage of the nest user?

Thank you in advance.

Cheers Christopher _______________________________________________ NEST Users mailing list -- users@nest-simulator.org To unsubscribe send an email to users-leave@nest-simulator.org