containerd namespaces — yessss
Why?
Because finally two different clients can have a container with the same ID/name without conflicting with each other. , making the dev flow so much more seamless.
In practice, if Jack and Jill both create the same container in their own namespace, and Jack deletes it, Jill will have no issues creating it again.
The point being that the delete applied only to Jack’s namespace.
To quote
Everything in containerd is namespaced, except for the namespace API, because it would be something out of a Christopher Nolan film and hard to reason about. — https://goo.gl/DTF8Lx
Mind you, I look forward to the inevitable Garbage-Collection issues 🤣
Comments