On Wed, Feb 2, 2011 at 6:25 PM, Trent W. Buck wrote:
> "Brian K. White" writes:
>
>> I just use 02:00: which ends up being automatically unique
>> enough to not collide with anything else on your subnet assuming you
>> already know the ip's you want to use
>>
>> IP=192.168.0.50 # container nic
On Fri, Feb 4, 2011 at 4:08 PM, Daniel Lezcano wrote:
> On 02/04/2011 03:43 PM, Andre Nathan wrote:
>> Hello
>>
>> I have the following container network configuration:
>>
>> lxc.network.type = veth
>> lxc.network.link = br0
>> lxc.network.flags = up
>> lxc.network.ipv4 = 192.168.0.2/24
>> lxc.net
On 02/04/2011 03:43 PM, Andre Nathan wrote:
> Hello
>
> I have the following container network configuration:
>
> lxc.network.type = veth
> lxc.network.link = br0
> lxc.network.flags = up
> lxc.network.ipv4 = 192.168.0.2/24
> lxc.network.name = eth0
>
> When the container starts up, this is how its
Hello
Let's say I have a file bind-mounted in read-only mode from the host to
the container. For example, /etc/resolv.conf.
In the container, I can use the mount command with the -oremount,rw
options and then edit the file from the container.
Is there a way to disable that behavior and forbid th
Hello
Is it possible to have everything inside a container (including init,
getty and whatever daemons are installed) being run as a normal user?
That is, can I have a container with no root user in /etc/passwd?
Thanks
Andre
--
Hello
I have the following container network configuration:
lxc.network.type = veth
lxc.network.link = br0
lxc.network.flags = up
lxc.network.ipv4 = 192.168.0.2/24
lxc.network.name = eth0
When the container starts up, this is how its eth0 interface is
configured:
eth0 Link encap:Ethernet
Hi,
looking at http://sourceforge.net/projects/lxc/ It is stated lxc is under LGPL
v3, in the code (both tarball and git repository) I saw LGPL v2.1
Are there code parts under the LGPL v3?
Bernd
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: