On Wed, Sep 9, 2015 at 11:48 AM, crequill wrote:
> 1/ I cannot login anymore on containers (/sbin/getatty exist in container):
> Failed to get login PTY: No such file or directory
No idea about your other issues, but I hit this one too and it is
fixed in systemd 2.26.
Kind regards,
Ruben
__
In container boot with : systemd-nspawn -bD
/var/lib/machines/ci-container/ -n
/sys/class/net show the host interfaces (enp3s1f0, ...)
ip link show only the interfaces lo and host0 (as desired)
Perhaps it's why netctl doesn't see the host0 interface
2015-09-09 11:48 GMT+02:00 creq
2015-09-09 9:39 GMT+03:00 Lennart Poettering :
> On Tue, 08.09.15 22:57, Alexey Shabalin (a.shaba...@gmail.com) wrote:
>
> > 2015-09-08 16:32 GMT+03:00 David Herrmann :
> >
> > > Hi
> > >
> > > Here's the next version of systemd, v226:
> > > * nspawn learnt support for .nspawn settings fil
Hi,
All was running fine with systemd 218.
With nspawn systemd 225, always on archlinux, I've a lot of problems:
1/ I cannot login anymore on containers (/sbin/getatty exist in container):
Failed to get login PTY: No such file or directory
2/ override of nspwawn file seems not to be charged (see
On 09/08/2015 07:48 PM, Simon McVittie wrote:
> On 08/09/15 13:55, Francis Moreau wrote:
>> On 09/08/2015 12:09 PM, Richard Maw wrote:
>>> I understood that the common configuration for socket activated sshd was to
>>> have a sshd.service for if you want it to always be running, and a pair of
>>> s
On 9/9/2015 PM 02:22, Steven Shiau wrote:
Well, you see that "bcache-probe" is invoked right before things go
bad? Whatever that is, maybe that's the problem? Have you tried
turning that rules file off?
Thanks. Yes, a few hours ago I disabled it by removing bcache-tools, and
the issue still re
