On Fri, Jun 7, 2013 at 3:45 PM, Purcareata Bogdan-B43198
wrote:
> Hello,
>
> I have a question regarding containers and their supporting rootfs. Is there
> an option for lxc-create that will use a default path (or other backing
> store) as rootfs?
Not that I know of.
However if you don't need
This probably applies to other wlan adapters, as the usb variety are
getting pretty cheap and it's probably preferable to just give a guest
complete ownership of the wlan device (not necessarily the phy, but the
ethernet interface).
Is this supported in any way, and are their any plans to? My dev
Hello,
I have a question regarding containers and their supporting rootfs. Is there an
option for lxc-create that will use a default path (or other backing store) as
rootfs?
I understand that by specifying -B ... it will try to _create_ the rootfs in an
alternate place. In my scenario, I plan
Good Morning,
Is there a config option available to specify the path of the executable
to start in the container?
I don't want /sbin/init and I don't want to rely on a symlink inside the
container.
I can specify it when starting a container like this "lxc-start -n
mycontainer /path/to/executa
Good Morning,
Is there a config option available to specify the path of the executable
to start in the container?
I don't want /sbin/init and I don't want to rely on a symlink inside the
container.
I can specify it when starting a container like this "lxc-start -n
mycontainer /path/to/executa
