On Wed, 2020-05-06 at 18:11 +0100, Simon McVittie wrote:
> On Wed, 06 May 2020 at 16:39:39 +0200, Lennart Poettering wrote:
> > On Do, 16.04.20 16:56, Simon McVittie (s...@collabora.com) wrote:
> > > /run/host seems like a reasonable convention to encourage for
> > > container/host systems that wan
On Wed, 06 May 2020 at 16:39:39 +0200, Lennart Poettering wrote:
> On Do, 16.04.20 16:56, Simon McVittie (s...@collabora.com) wrote:
> > /run/host seems like a reasonable convention to encourage for
> > container/host systems that want this, since it doesn't require
> > inventing a new top-level di
On Do, 16.04.20 16:56, Simon McVittie (s...@collabora.com) wrote:
> On Thu, 16 Apr 2020 at 14:03:43 +, Luca Boccassi wrote:
> > But I found at least one other use case where this is needed, and the
> > solution there is to add a new directory /host/ which replicates part
> > of the host's file
On Do, 16.04.20 14:03, Luca Boccassi (luca.bocca...@microsoft.com) wrote:
> Hi,
>
> We find ourselves in a situation where application running
> containerized (specifically as portable services, although this issue
> is general) need to either find information about the host, or alter
> their beha
On Thu, 16 Apr 2020 at 14:03:43 +, Luca Boccassi wrote:
> But I found at least one other use case where this is needed, and the
> solution there is to add a new directory /host/ which replicates part
> of the host's filesystem tree, including os-release:
>
> https://docs.netdata.cloud/packagin
Hi,
We find ourselves in a situation where application running
containerized (specifically as portable services, although this issue
is general) need to either find information about the host, or alter
their behaviour depending on the host's flavour.
At the same time, applications also need to fin
