#766216: lxc: can't access console or stop a jessie container running systemd as PID 1

[Tomas Pospisek]

On Sun, 7 Dec 2014, Adam D. Barratt wrote:

> Is this still relevant after the upload of lxc 1.0.6-5?

I can confirm that *this specific* problem, namely #766216 - not 
beeing able to access the console or to stop the VM" has indeed been 
fixed in 1:1.0.6-5 on a host running up to date jessie with a freshly 
created jessie VM.

There are still a few ugly things happening when starting the container:

    # lxc-start -n testfoo
    [...]
    Failed to open /dev/autofs: No such file or directory
    Failed to initialize automounter: No such file or directory
    [FAILED] Failed to set up automount Arbitrary Executable File Formats
    File System Automount Point.
    See 'systemctl status proc-sys-fs-binfmt_misc.automount' for details.
    [...]
    [FAILED] Failed to start Login Service.

but the container startup proceeds to the login prompt and loging in works 
so the above is - if ever - material for a different bug report.
*t