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

initContainer: also create mount points for sockets #1576

Closed

Conversation

jbtrystram
Copy link
Contributor

When a socket is bind-mounted to the container, also create a file mount point for it. Nvidia CDI on the proprietary driver added a socket for nvidia-persistence.service which was failing to be mounted in the container as no mount point existed.

More logs in the issue below.
Fixes #1572

When a socket is bind-mounted to the container, also create a file
mount point for it. Nvidia CDI on the proprietary driver added a
socket for `nvidia-persistence.service` which was failing to be mounted
in the container as no mount point existed.

More logs in the issue below.
Fixes containers#1572
Copy link
Member

@debarshiray debarshiray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the patch @jbtrystram ! This looks correct to me. However, I am about to leave for an extended weekend, so I am not in a position to test it. I will get it merged once I am back on Tuesday.

Thanks again!

Copy link
Member

@debarshiray debarshiray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works perfectly in my testing! Thanks!

Oddly, I can't force push after rebasing against main:

$ git push --force jbtrystram mount_nvidia_peristence_socket:jbtrystram/mount_nvidia_peristence_socket 
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 16 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 847 bytes | 847.00 KiB/s, done.
Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
To github.com:jbtrystram/ctrs-toolbox.git
 ! [remote rejected]           mount_nvidia_peristence_socket -> jbtrystram/mount_nvidia_peristence_socket (permission denied)
error: failed to push some refs to 'github.com:jbtrystram/ctrs-toolbox.git'

... so, I pushed it to #1577

Waiting for the CI to finish.

@jbtrystram
Copy link
Contributor Author

Weird. I'll close this then

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

Successfully merging this pull request may close these issues.

Entering fails if NVIDIA Persistence Daemon is used
2 participants