Bug#946725: debug.log with different umasks

2020-01-12 Thread bauerfichtner
I managed to verify that the issue is indeed tied to the umask, as in this issue: https://github.com/lxc/lxc/issues/3100 When executing the following command, the container does not successfully boot: (umask 077; sudo lxc-start --name test --logfile debug.077.log --logpriority TRACE) When exec

Bug#946725: Requested debug.log

2020-01-05 Thread bauerfichtner
Hi, sorry for the delay. I attached the requested debug.log. lxc-start test 20200105141353.962 INFO confile - confile.c:set_config_idmaps:1605 - Read uid map: type u nsid 0 hostid 886432 range 65536 lxc-start test 20200105141353.963 INFO confile - confile.c:set_config_idmaps:1605 - Read

Bug#946725: Additional information

2019-12-15 Thread bauerfichtner
I just found out that unprivileged container start just fine if they are configured to start automatically during system (and lxc) startup. I also found https://github.com/lxc/lxc/issues/3100 but could not yet confirm that it is in fact root's umask that is causing the unprivileged containers to

Bug#946725: lxc: Unprivileged containers fail with 'Failed to mount API filesystems'

2019-12-14 Thread bauerfichtner
Package: lxc Version: 1:3.1.0+really3.0.3-8 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Created an unprivileged container. * What exactly did you do (or not do) that was effective (