[lxc-users] lxd: Can't write to /dev/console

[Stéphane Graber]

On Thu, Feb 04, 2016 at 11:33:24AM +0000, Matt Willsher wrote:
> Hi, 
> 
> I've create a container, using lxd, based on the ubuntu wily cloud image. In cloud-init I'm calling 
> 
> power_state:
>   mode: reboot
>   timeout: 30
>   condition: True
> 
> But in the cloud-init logs in the container I get:
> 
> Feb  4 11:21:00 ubuntu [CLOUDINIT] util.py[DEBUG]: Failed forking and calling callback run_after_pid_gone#012Traceback (most recent call last):#012  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 285, in fork_cb#012    child_cb(*args, **kwargs)#012  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_power_state_change.py", line 209, in run_after_pid_gone#012    time.sleep(.25)#012  File "/usr/lib/python3/dist-packages/cloudinit/signal_handler.py", line 62, in _handle_exit#012    console=True, stderr=False, log=LOG)#012  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 434, in multi_log#012    with open(conpath, 'w') as wfh:#012PermissionError: [Errno 13] Permission denied: '/dev/console'
> 
> Is there a way to make /dev/console writable? 
> 
> Thanks,
> Matt

raw.lxc: |
    lxc.console=
    lxc.cgroup.allow=c 5:1 rwx

That or wait for lxd 2.0.0.beta2 (next Tuesday) which will have
/dev/console writable again.

We turned off writes to it to make CRIU happy, but then noticed that a
lot of userspace binaries don't cope well with it missing so I reverted
this a couple of days ago upstream and we'll have to find a way to make
CRIU work with this setup.

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20160204/44c25841/attachment.sig>