Quoting Fajar A. Nugraha (l...@fajar.net):
> On Thu, Apr 21, 2016 at 11:21 PM, Harald Dunkel wrote:
> > On 04/21/16 08:05, Fajar A. Nugraha wrote:
> >> On Wed, Apr 20, 2016 at 6:50 PM, Harald Dunkel
> >> wrote:
> >>> Hi folks,
> >>>
> >>> AFAIR the idea of the containers was to provide isolation
On Thu, Apr 21, 2016 at 11:21 PM, Harald Dunkel wrote:
> On 04/21/16 08:05, Fajar A. Nugraha wrote:
>> On Wed, Apr 20, 2016 at 6:50 PM, Harald Dunkel
>> wrote:
>>> Hi folks,
>>>
>>> AFAIR the idea of the containers was to provide isolation
>>> between the host and the user-space instances.
>>>
>
On 04/21/16 08:05, Fajar A. Nugraha wrote:
> On Wed, Apr 20, 2016 at 6:50 PM, Harald Dunkel
> wrote:
>> Hi folks,
>>
>> AFAIR the idea of the containers was to provide isolation
>> between the host and the user-space instances.
>>
>> Are we loosing this with systemd support?
>
> What makes you t
On Wed, Apr 20, 2016 at 6:50 PM, Harald Dunkel wrote:
> Hi folks,
>
> AFAIR the idea of the containers was to provide isolation
> between the host and the user-space instances.
>
> Are we loosing this with systemd support?
What makes you think that?
The host only needs systemd cgroup mount, it d
Hi folks,
AFAIR the idea of the containers was to provide isolation
between the host and the user-space instances.
Are we loosing this with systemd support?
Regards
Harri
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.lin
Hi,
>>> On Wed, 20 Apr 2016 09:13:26 +0200
in message "Re: [lxc-users] sysvinit with cgroup namespace"
Harald Dunkel-san wrote:
> I tried, but it did not work:
> # grep /sys/fs/cgroup /etc/fstab
> systemd /sys/fs/cgroup cgroup none,name=syst
On Wed, Apr 20, 2016 at 2:13 PM, Harald Dunkel wrote:
> I tried, but it did not work:
>
> # grep /sys/fs/cgroup /etc/fstab
> systemd /sys/fs/cgroup cgroup none,name=systemd
Should be
# grep systemd /proc/mounts
cgroup /sys/fs/cgroup/systemd cgroup rw,relatime,clone_children,name=systemd 0 0
name
Hi Serge,
On 04/06/16 17:18, Serge Hallyn wrote:
> Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp):
>>
>> Will we be able to start a container on sysvinit with cgroup namespace
>> in the future release?
>
> mkdir /sys/fs/cgroup
> mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup
>
> Yo
On 04/06/2016 05:18 PM, Serge Hallyn wrote:
> Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp):
>>
>> Will we be able to start a container on sysvinit with cgroup namespace
>> in the future release?
>
> mkdir /sys/fs/cgroup
> mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup
>
Or was it
Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp):
> Sorry, I ran old version (2.0.0.rc7).
>
> > My desktop is used sysvinit as init.
>
> > I try using the "cgroup namespace", then a lxc container does not
> > start.
>
> > Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup
> > d
Quoting KATOH Yasufumi (ka...@jazz.email.ne.jp):
> Hi,
>
> My desktop is used sysvinit as init.
>
> I try using the "cgroup namespace", then a lxc container does not
> start.
>
> Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup
> driver (in cgfsng_opt_init function). But in
Sorry, I ran old version (2.0.0.rc7).
> My desktop is used sysvinit as init.
> I try using the "cgroup namespace", then a lxc container does not
> start.
> Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup
> driver (in cgfsng_opt_init function). But in all_controllers_found
>
Hi,
My desktop is used sysvinit as init.
I try using the "cgroup namespace", then a lxc container does not
start.
Now, If we have '/proc/self/ns/cgroup', then cgfsng is used as cgroup
driver (in cgfsng_opt_init function). But in all_controllers_found
function (in cgfsng.c), systemd cgroup ("name
13 matches
Mail list logo
