[Lxc-users] adding a default gateway inside a container as a non root user

[Serge Hallyn]

Quoting Bekir Dogan (bekirdo at gmail.com):
> Hi Daniel,
> 
> On Thu, Mar 1, 2012 at 23:20, Daniel Lezcano <daniel.lezcano at free.fr> wrote:
> > [...]
> > With the 0.8.0 version, you will be able to setup the gateway directly
> > from the configuration file.
> 
> Can we see project plans or a todo list or something like these which
> gives us about the future features should come in next releases. I
> can't find something like this in a TODO file, open bug reports or a
> special page in sourceforge. Or do you suggest something to follow
> other than these.
> 
> I'm about to start a project
> (https://github.com/bergerx/simplelxc#readme) for mainly laptop users
> to create and manage networking enabled test containers so simply
> which also setup initial networking for both lxc containers and host
> system.
> 
> I would like to use networking as it should be and determine the
> project direction according to this or I should be in a position to
> re-implement some parts.
> 
> I've talked implementing some ideas into debian lxc package Daniel
> Baumann mainy about a simple creation scenario without asking anything
> other than container name.

Right now in ubuntu precise, it's

    lxc-create -t ubuntu -n p1
    lxc-start -n p1

or

    lxc-create -t ubuntu-cloud -n p1
    lxc-start -n p1

If you want to deploy a bunch of cloned images, you can

    lxc-create -t ubuntu -n plain -B lvm
    < customize /dev/lxc/plain image if you like >
    for i in `seq 1 20`; do
        lxc-clone -s -o plain -n p$i
    done

The only things different in Ubuntu are that a lxcbr0 bridge gets
installed by default (*1), and the release has been tweaked a bit so no
changes are needed to run in a container.  The first can't really
be done in lxc.git (because it's distro-dependent), and the second
is of course independent of lxc.

-serge

(*1) and if you don't specify a configuration file at creation time,
a default one using lxcbr0 is used.