Repository navigation
Commit 2b34f1f
committed
CI: re-bind /run/nvidia-persistenced into container after driver swap
The container's bind mount of /run/nvidia-persistenced/ is taken at
container-start time and pinned to the host directory's then-current
inode. Across the install the host directory gets recreated under a
fresh inode (the daemon's shutdown + restart cycle replaces it), and
the container is stranded on the deleted inode -- socket file shows
up with link count 0 inside the container, NVML state-changing calls
return NVML_ERROR_UNKNOWN.
After refresh_container_libs, umount the stale bind, mkdir the local
mount point if missing, and re-bind from /proc/1/root/run/nvidia-
persistenced (the host's current view via the privileged container's
host-pid-ns access). CAP_SYS_ADMIN required, which custom-DRIVER rows
already grant via --privileged --pid=host.1 parent 6412f4f commit 2b34f1f
1 file changed
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
227 | 227 | | |
228 | 228 | | |
229 | 229 | | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
230 | 248 | | |
231 | 249 | | |
232 | 250 | | |
| |||
0 commit comments