[lxc-users] sshd-keygen fails during container boot

[Peter Steele]

On 12/08/2015 08:36 PM, Serge Hallyn wrote:
> What do you mean by "when the server comes up"?  If you bring up the
> server, let it set for 5 mins, then start them, they still fail?
What I meant here was that when my server boots, it launches our 
management software, which in turns launches the containers that are 
defined on that server. The systemd errors occur as the containers are 
started. Delaying when the containers are started doesn't have any 
effect. I've found though that if I put a five second delay between 
starting each container, the systemd errors don't occur (at least not in 
the tests I've run so far). I haven't had this issue with libvirt-lxc, 
and I hope there is a better solution than this arbitrary five second delay.
> What lxc version are you using again? 
1.1.5.
>> Ok, so this shows that in the container 'sys/fs' existed,
>> but fuse did not.  This suggests that the fuse kernel module
>> was not done loading yet.
>>
>> Could you add to /lib/systemd/system/lxc.service the line
>>
>> ExecStartPre=modprobe fuse
>>
>> and see if that helps?  (I'm not sure if you'd also need to sleep
>> a short time to give syfs time to catch up, or if the modprobe
>> would wait...  you could just use a script that waits until
>> /sys/fs/fuse exists on the host)
>>
I added this line to lxc.service and that cleared up the fuse issues. 
This did not have any effect on the systemd errors though.

Peter