Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> I do start them as non-root user because I tough I was the only way to start
> an unprivileged container on the system.
Ok, that's what I was wondering. In order to start such containers
as root, you only need to ma
to allow the unprivileged user to specify a script
to run as root :) But if we can come up with a program that is shipped with
lxc, that may be doable.
> I don't know how software like Openstack or Proxmox are integrating LXC
> Unprivileged container but they should talk/share more ab
is to allow the unprivileged user to specify a script
to run as root :) But if we can come up with a program that is shipped with
lxc, that may be doable.
> I don't know how software like Openstack or Proxmox are integrating LXC
> Unprivileged container but they should talk/share more about
tack or Proxmox are integrating LXC
Unprivileged container but they should talk/share more about it ^^
Regards,
Cordialement,
Benoît Georgelin
De: "Serge Hallyn"
À: "lxc-users"
Envoyé: Lundi 31 Août 2015 09:39:01
Objet: Re: [lxc-users] Unprivileged contain
Quoting Benoit GEORGELIN - Association Web4all (benoit.george...@web4all.fr):
> Hi,
>
> I would like to know if there is an alternative option of
> lxc.network.script.up with an unprivileged containter.
No. You'll need to start the container as root to do that - else you're
allowing an unpriv
Hi,
I would like to know if there is an alternative option of lxc.network.script.up
with an unprivileged containter.
It looks like this configuration file is not used.
I would like to use script.up and script.down to manage the network and
Openflow configuration
Every time a containter star
