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

Accessing GPU in Google Colab with udocker #425

Open
yimingsun12138 opened this issue May 9, 2024 · 0 comments
Open

Accessing GPU in Google Colab with udocker #425

yimingsun12138 opened this issue May 9, 2024 · 0 comments

Comments

@yimingsun12138
Copy link

Hi udocker Team,

Firstly, I'd like to express my appreciation for your remarkable efforts on the udocker project. It has significantly streamlined my workflows as a data scientist, especially for running various containers on Google Colab.

I am currently exploring the possibility of leveraging Google Colab's GPU within a udocker container. I attempted to enable GPU access by using the udocker setup with Nvidia support via the following steps:

!apt install screen
!pip install udocker
!udocker --allow-root install
!udocker --allow-root pull nvidia/cuda:12.4.1-cudnn-devel-ubuntu22.04

!screen -d -m udocker --allow-root run nvidia/cuda:12.4.1-cudnn-devel-ubuntu22.04 /bin/bash
!sleep 120

!udocker --allow-root ps

After retrieving the container ID, I proceeded with the Nvidia setup:

!udocker --allow-root setup --nvidia 62d47422-512d-3856-b1e5-55619651bbfd

However, I encountered some errors during the setup:

Info: Cont, has files from previous nvidia install
Error: creating nvidia dir /root/.udocker/containers/62d47422-512d-3856-b1e5-55619651bbfd/ROOT//etc/vulkan/icd.d
Warn: nvidia file in config not found /etc/vulkan/icd.d/nvidia_icd.json
Error: creating nvidia dir /root/.udocker/containers/62d47422-512d-3856-b1e5-55619651bbfd/ROOT//etc/OpenCL/vendors
Warn: nvidia file in config not found /etc/OpenCL/vendors/nvidia.icd
Info: nvidia mode set

I have no idea how to resolve these errors. Could you provide any guidance or suggestions to help address this issue? Any assistance would be greatly appreciated.

Thank you for your support and for continuing to improve this amazing tool.

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

No branches or pull requests

1 participant