Hi Dan. Dan Smith <danms@xxxxxxxxxx> wrote: > (apologies if you see this multiple times...IBM mail server troubles) > > This patch adds a "phase" of c/r that saves out information about any > namespaces the task(s) may have. Do this by tracking the nsproxy of the > first task and making sure that the tasks that follow get hooked back to > share the same one on restart. On restart, we also explicitly create new > namespaces for any that we support at the first task. I'd like there to be some discussion about this, because namespace creation seems like a significant addition to the semantics of restart as I understand it. Is namespace creation during restart unavoidable, or merely desirable? Is there a case for requiring the user to provide a suitable namespace environment before attempting restart? _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
