Public bug reported:
Running lxc-stop on a container which doesn't exist actually creates the
container, and messes up its permissions, causing sequences like:
$ lxc-stop -n foo lxc-destroy -n foo lxc-clone clean-machine foo
..to fail with bad errors:
# it definitely doesn't exist to start
Public bug reported:
Running lxc-stop on a container which doesn't exist actually creates the
container, and messes up its permissions, causing sequences like:
$ lxc-stop -n foo lxc-destroy -n foo lxc-clone clean-machine foo
..to fail with bad errors:
# it definitely doesn't exist to start
