Skip to content
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

Running the notebook on Podman #273

Open
rnanclares opened this issue May 24, 2022 · 1 comment
Open

Running the notebook on Podman #273

rnanclares opened this issue May 24, 2022 · 1 comment

Comments

@rnanclares
Copy link

rnanclares commented May 24, 2022

For people interested in running the notebooks with Podman (Fedora, RHEL, Almalinux, etc). You can run the notebooks without any issue with the following commands:

# These two first commands allow the container user to write into a directory in your system, usually in the /home/user/ path
podman unshare chown -R 1000:100 ./book/data/
podman unshare chown -R 1000:100 ./book/notebooks/
# actually the directory that needs to be owned by the user inside the container is ./book/notebooks/cache but it doesn't exist until you run the 03_spatial_data notebook the first time).
# To download the image from Docker hub and run the container use the next command
podman run --privileged --name book -it --rm -p 8888:8888 -v ./book/:/home/jovyan/work darribas/gds:7.0

Why do we need to do this? Some of the code in the notebooks creates outputs in local directories and Podman has more security restrictions than Docker, and it usually doesn't needs to be run with sudo or as root. If you don't want to change the permissions on your system you can run the container using sudo.

Hope this is helpful to anybody trying to follow the book using podman.

Cheers.

@darribas
Copy link
Member

Thank you very much @rnanclares!!! Will leave the issue open until we can see how we can include this on the website/blog to give it more visibility, I think it's very useful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants