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
`verifyNoStaleFiles` in `tests/e2e/utils.go` checks containerd task paths under `default` and `k8s.io` but does not check the `moby` namespace. Docker
uses the `moby` namespace for containerd tasks. As a result, post-test stale file verification never catches leftover containerd task directories when tests
run with Docker, which defeats the purpose of the check.
The `moby` path used by Docker is not checked. A stale directory under `/run/containerd/io.containerd.runtime.v2.task/moby/` will not be
detected and the function returns nil.
Expected Behavior
`verifyNoStaleFiles` should verify all three containerd namespaces that urunc can place task directories under: `default`, `k8s.io`, and `moby`.
Description
`verifyNoStaleFiles` in `tests/e2e/utils.go` checks containerd task paths under `default` and `k8s.io` but does not check the `moby` namespace. Docker
uses the `moby` namespace for containerd tasks. As a result, post-test stale file verification never catches leftover containerd task directories when tests
run with Docker, which defeats the purpose of the check.
Fixes #64
Current Behavior
Only two task paths are checked:
The `moby` path used by Docker is not checked. A stale directory under `/run/containerd/io.containerd.runtime.v2.task/moby/` will not be
detected and the function returns nil.
Expected Behavior
`verifyNoStaleFiles` should verify all three containerd namespaces that urunc can place task directories under: `default`, `k8s.io`, and `moby`.