The lxc-execute command is used for 'application container'. Usually, the system container uses a rootfs and the application container do not use a rootfs. So lxc is looking for if the rootfs option is set and then setup the console.
Here lxc-execute is used with the rootfs, so it setup the console, that is to say it maps /dev/console to /dev/tty. Of course, that makes sense only if we have the applications writing to /dev/console which is the case when the system containers boot. Doing that with a shell is messy and we have problem with the tty. => Why is needed a rootfs with lxc-execute ? There are 2 solutions to fix this problem: (1) do not specify the rootfs but ro-bind-mount the <rootfs>/usr to /usr and the other needed directories. (2) change the code to have lxc-execute to take into account a rootfs but I wouldn't recommend that because that will bring much more complexity and more errors with the console by adding a new configuration combination. At least we should decide to ignore the rootfs option when lxc-execute is used. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/986956 Title: lxc-execute does not work with commands that require input from terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/986956/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs