I didn't expect it.
While I understand that there is no such entity as "a container" on
linux, the functionality of lxc being a construct of several underlying
features, lxc appears to me to be trying to construct a consistent
abstraction on those features. The unit of reference throughout the
doc
Public bug reported:
If lxc-execute is passed a non-existent container name, then the command
given is run in the current namespace.
I believe it should failed with a "container not found" error, as
otherwise it can lead to unexpected consequences in the host
environment.
example:
# lxc-ls
file
