On 02/07/2011 01:32 AM, Trent W. Buck wrote:
> Daniel Lezcano writes:
>
>> 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
Nirmal Guhan writes:
> 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
Matto Fransen writes:
>> In the container, I can use the mount command with the -oremount,rw
>> options and then edit the file from the container.
>
> So the bind read-only mounts are no protection against changing the
> filesystem of the container, but even makes it possible to corrupt the
> _ho
Daniel Lezcano writes:
> 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 th
On Sun, 06 Feb 2011 18:23:41 +1300, Gary Ballantyne
wrote:
> On 2/6/2011 3:56 PM, John Drescher wrote:
>>> Is this important if, say, a malicious user has access to a container?
>>> Or, can a container be configured such that they could do little harm?
>>
>> You can easily make a container have i
Hi,
On Fri, Feb 04, 2011 at 04:39:57PM -0200, Andre Nathan wrote:
> 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 fr
