Re: [PATCH] uts_namespace: Move boot_id in uts namespace

On 04/05/2018 03:35 AM, Eric W. Biederman wrote: > Marian Marinov writes: > >> On 04/04/2018 07:02 PM, Eric W. Biederman wrote: >>> Angel Shtilianov writes: >>> Currently the same boot_id is reported for all containers running on a host node, including the host node itself. Even after

Re: [PATCH] uts_namespace: Move boot_id in uts namespace

Marian Marinov writes: > On 04/04/2018 07:02 PM, Eric W. Biederman wrote: >> Angel Shtilianov writes: >> >>> Currently the same boot_id is reported for all containers running >>> on a host node, including the host node itself. Even after restarting >>> a container it will still have the same pe

Re: [PATCH] uts_namespace: Move boot_id in uts namespace

On 04/04/2018 07:02 PM, Eric W. Biederman wrote: > Angel Shtilianov writes: > >> Currently the same boot_id is reported for all containers running >> on a host node, including the host node itself. Even after restarting >> a container it will still have the same persistent boot_id. >> >> This can

Re: [PATCH] uts_namespace: Move boot_id in uts namespace

Angel Shtilianov writes: > Currently the same boot_id is reported for all containers running > on a host node, including the host node itself. Even after restarting > a container it will still have the same persistent boot_id. > > This can cause troubles in cases where you have multiple container

[PATCH] uts_namespace: Move boot_id in uts namespace

Currently the same boot_id is reported for all containers running on a host node, including the host node itself. Even after restarting a container it will still have the same persistent boot_id. This can cause troubles in cases where you have multiple containers from the same cluster on one host