-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Problem running with podman on HPC #5
Comments
Most likely due to jupyterlab-r-docker-stack/base/scripts/usr/local/bin/before-notebook.d/11-home.sh Lines 9 to 10 in bfcd656
|
jupyterlab-r-docker-stack/base/scripts/usr/local/bin/start.sh Lines 13 to 15 in bfcd656
This might not be required when run as @bernt-matthias I will look into this and provide a patched image so you can test it on the HPC. |
Excellent. Thanks a lot |
@bernt-matthias Try with podman run --rm \
-p 8888:8888 \
-u root \
-e NB_USER=root \
-e NB_UID=0 \
-e NB_GID=0 \
-e NOTEBOOK_ARGS="--allow-root" \
glcr.b-data.ch/jupyterlab/r/base:test-hpc Thanks for your feedback. |
Seems that it gets closer, but there is still some error:
|
That is due to jupyterlab-r-docker-stack/base/scripts/usr/local/bin/start.sh Lines 240 to 244 in bfcd656
Let me see what I can do... |
@bernt-matthias I patched the image once more. Please pull |
There seem to be two files with unexpected permissions:
|
@bernt-matthias Try with podman run --rm \
-p 8888:8888 \
-u root \
-e NB_UMASK=0077 \
-e NB_USER=root \
-e NB_UID=0 \
-e NB_GID=0 \
-e NOTEBOOK_ARGS="--allow-root" \
glcr.b-data.ch/jupyterlab/r/base:test-hpc |
Or (better) podman run --rm \
-p 8888:8888 \
-u root \
-e NB_USER=root \
-e NB_UID=0 \
-e NB_GID=0 \
-e JUPYTER_ALLOW_INSECURE_WRITES=true \
-e NOTEBOOK_ARGS="--allow-root" \
glcr.b-data.ch/jupyterlab/r/base:test-hpc |
Or (alternatively) podman run --rm \
-p 8888:8888 \
-u root \
-e NB_USER=root \
-e NB_UID=0 \
-e NB_GID=0 \
-e export JUPYTER_RUNTIME_DIR=/directory/not/in/mounted/filesystem \
-e NOTEBOOK_ARGS="--allow-root" \
glcr.b-data.ch/jupyterlab/r/base:test-hpc should Cross reference: |
You have quite an edge case here... (Openshift?) Because on a regular Linux machine, the mentioned files have permission |
This worked :) |
Could you explain to me the connection between jupyter and rocker/rstudio? |
There is none. These are separate projects. |
The Jupyter Docker Stacks do not include RStudio. |
What makes this project different:
|
Does everything work as expected when you access in a browser? What about the permissions? Could you please open the JupyterLab Terminal, execute mkdir test-folder
touch test-file
ls -al and post the output here? Alternative: podman run -it --rm \
-u root \
-e NB_USER=root \
-e NB_UID=0 \
-e NB_GID=0 \
-e JUPYTER_ALLOW_INSECURE_WRITES=true \
-e NOTEBOOK_ARGS="--allow-root" \
glcr.b-data.ch/jupyterlab/r/base:test-hpc bash (For direct Zsh access you should install the recommended font on the host) |
@bernt-matthias I will do some further tests. If nothing unexpected occurs, all JupyterLab docker stacks will be patched tomorrow. |
Everything as expected:
|
But I did not notice the following in the terminal running the container
|
There will be one or the other error message. The question is whether code-server and RStudio work smoothly. |
Code server worked. RStudio failed. |
What does it output/log? |
After the link + token is reported the output is:
|
RStudio should work once v2024.10 is out and is merged. |
This just gives me:
Error: OCI runtime error: crun: cannot setresgid to
100: Invalid argument
This seems to do much more:
But there is an error in the "end":
runuser: cannot set groups: Operation not permitted
Originally posted by @bernt-matthias in rocker-org/rocker-versioned2#838 (comment)
The text was updated successfully, but these errors were encountered: