On Tue, 28 Jan 2020 15:28:08 +0300
"Matwey V. Kornilov" wrote:
> вт, 28 янв. 2020 г. в 15:25, Lennart Poettering
> :
> > We document the requirements and expectations to run systemd in
> > containers very explicitly here:
> >
> > https://systemd.io/CONTAINER_INTERFACE
>
> If I could google
вт, 28 янв. 2020 г. в 15:25, Lennart Poettering :
>
> On Di, 28.01.20 15:07, Matwey V. Kornilov (matwey.korni...@gmail.com) wrote:
>
> > Thanks for reply! I've just wanted to let you know about this issue
> > after spending couple hours trying to understand why my container
> > works on the one
On Di, 28.01.20 15:07, Matwey V. Kornilov (matwey.korni...@gmail.com) wrote:
> Thanks for reply! I've just wanted to let you know about this issue
> after spending couple hours trying to understand why my container
> works on the one host and don't work on another one.
> I think there are couple
вт, 28 янв. 2020 г. в 11:36, Lennart Poettering :
>
> On So, 26.01.20 11:55, Matwey V. Kornilov (matwey.korni...@gmail.com) wrote:
>
> > Hello,
> >
> > I've just found that an assumption used inside detect_container() is
> > not always true, and that leads to virtualization misdetection.
> >
On So, 26.01.20 11:55, Matwey V. Kornilov (matwey.korni...@gmail.com) wrote:
> Hello,
>
> I've just found that an assumption used inside detect_container() is
> not always true, and that leads to virtualization misdetection.
> Namely, I am running systemd inside docker (19.03.5) container on
>
Hello,
I've just found that an assumption used inside detect_container() is
not always true, and that leads to virtualization misdetection.
Namely, I am running systemd inside docker (19.03.5) container on
ubuntu (18.04.2 kernel version is 4.15.0-45-generic).
/* Interestingly
