Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug]: container-toolkit DaemonSet: containerd-socket hostPath volume lacks mountPropagation: HostToContainer, pins host ZFS mounts and blocks zfs destroy ("dataset is busy")

Aperta
  • Qualcosa non va?
#3,083 1 commento 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@rahulait ci sta già lavorando.

Dal 19/10/2026.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
devops, infrastructure

Direzione di ricerca

The fix sits in the toolkit DaemonSet's volume definitions, specifically the containerd-socket hostPath volume, which lacks mountPropagation: HostToContainer. Find where the operator generates that DaemonSet and compare it with the host-root and driver-install-dir volumes. To reproduce, mount a ZFS dataset, restart the toolkit pod, unmount, then check /proc/<pid>/mountinfo and zfs destroy. Done when the destroy succeeds without a container restart and the setting survives operator reconciliation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug needs-triage

Problem

The nvidia-container-toolkit-daemonset in GPU Operator v26.7.1 mounts these hostPath volumes:

volume hostPath mountPath mountPropagation
host-root / /host HostToContainer
driver-install-dir /run/nvidia/driver /driver-root HostToContainer
containerd-socket /run/containerd /runtime/sock-dir/ not set (private)

The toolkit container's own rootfs lives under /run/containerd. Its /host sub-mount carries every host mount, including all ZFS datasets. Because containerd-socket is a private recursive bind, the whole mount tree is copied into the container's mount namespace when the container starts. After that, the copy never receives unmount events from the host.

Impact

  • Any ZFS dataset that is mounted on the host when the toolkit container starts stays pinned in the container's mount namespace.
  • Later, the host unmounts the dataset, and it reports mounted=no. But zfs destroy still fails with cannot destroy '': dataset is busy.
  • The dataset stays undeletable until the toolkit container restarts. The restart re-pins every dataset that exists at that moment.
  • This affects every container restart, including node reboots. Datasets created after the container starts are not affected.

Evidence

After the dataset is unmounted on the host, its mount entries are still found in the toolkit process's mount namespace:
$ grep -l /proc/[0-9]*/mountinfo
/proc//mountinfo # comm=nvidia-toolkit
.../runtime/sock-dir/io.containerd.runtime.v2.task/k8s.io//rootfs/host/ - zfs

Environment

  • NVIDIA GPU Operator v26.7.1 (Helm chart gpu-operator-v26.7.1)
  • OS: Ubuntu 24.04
  • Kernel Version: 6.8.0-142-generic
  • Container Runtime Version: containerd v2.1.4
  • Container-toolkit image: nvcr.io/nvidia/k8s/container-toolkit:v1.20.1
  • GPU Driver: 580.105.08
  • Host filesystems: ZFS datasets mounted on the host
  • Kubernetes Distro and Version: Kubelet v1.33.5

Steps to reproduce

  1. Create and mount a ZFS dataset on a GPU node.
  2. Restart the nvidia-container-toolkit pod on that node, or reboot the node.
  3. Unmount the dataset on the host and run zfs destroy -r .
  4. The destroy fails with dataset is busy. The dataset's mount is still listed in the toolkit process's /proc//mountinfo.

Requested fix

Set mountPropagation: HostToContainer on the containerd-socket volume, the same as host-root and driver-install-dir, so that host unmounts propagate into the container. A setting in ClusterPolicy to configure it would also work. Patching the DaemonSet by hand isn't a durable workaround because the operator reconciles it back.

Lingua principale
Go
Stelle
2.9k
Fork
576
Merge medio
1g 5h
PR unite (30g)
65

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/gpu-operator

Tutte le issue di NVIDIA/gpu-operator

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.