Daniel Lezcano writes:
> Hi Serge,
>
> thanks for the pointer.
>
> I though it was for user ns only.
The pieces were closely interrelated so I used the same tree.
> Cool to see Eric is taking care of the final bits of this feature.
My apologies for letting it languish so long. That wasn't my
These states are kept by the kernel in the freezer.state cgroup item, and
are never set in handler->state with lxc_set_state(). If lxc transitions
a container to/from the freezer after an lxc-wait for one of the above
states has already started, the lxc-wait will never see the new state. This
chang
Currently, lxc-destory will attempt to destroy a container if it is not in
the RUNNING state, but doing so is not good when the container is FROZEN, or
in other transitional states.
Signed-off-by: Dwight Engen
---
src/lxc/lxc-destroy.in | 8
1 file changed, 4 insertions(+), 4 deletions(
