You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current nerdctl implementation sets a global default snapshotter (overlayfs), which overrides containerd's namespace-specific snapshotter configuration defined via namespace labels (ref). According to containerd's design, the default snapshotter for a namespace is resolved only when no snapshotter is explicitly specified.
Steps to reproduce the issue
Configure a containerd namespace (e.g., k8s.io) with a label containerd.io/snapshotter=devmapper.
Run nerdctl -n k8s.io run ... without specifying --snapshotter.
Observe that nerdctl still uses overlayfs instead of the namespace-configured devmapper.
Describe the results you received and expected
If no --snapshotter is provided, nerdctl should defer to containerd's resolution logic, honoring namespace-level defaults.
What version of nerdctl are you using?
v2.0.4
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response
The text was updated successfully, but these errors were encountered:
Description
The current nerdctl implementation sets a global default snapshotter (overlayfs), which overrides containerd's namespace-specific snapshotter configuration defined via namespace labels (ref). According to containerd's design, the default snapshotter for a namespace is resolved only when no snapshotter is explicitly specified.
Steps to reproduce the issue
Describe the results you received and expected
If no --snapshotter is provided, nerdctl should defer to containerd's resolution logic, honoring namespace-level defaults.
What version of nerdctl are you using?
v2.0.4
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
No response
The text was updated successfully, but these errors were encountered: