Adding -s lxc.tty=1 -s lxc.console=/dev/console for interactive
processes works for me:
sudo lxc-execute -n test /bin/bash -s lxc.rootfs=/ -s lxc.tty=1 -s
lxc.console=/dev/console
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
I am seeing this behavior too on 12.04. I must specify lxc.aa_profile =
unconfined, and I must omit a rootfs setting, for lxc-execute to work
with anything interactive like bash or python.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The last comments make me think that lxc-execute works with application
containers. Does it work?
The simplest usage would be (without a created container test):
$ sudo lxc-execute -n test /bin/bash
But due to bug 981955 this does not work. With the workaround there:
$ sudo lxc-execute -n test
Quoting B Clausius (ba...@gmx.de):
The last comments make me think that lxc-execute works with application
containers. Does it work?
The simplest usage would be (without a created container test):
$ sudo lxc-execute -n test /bin/bash
But due to bug 981955 this does not work. With the
