Quoting Michael Adam (ob...@samba.org):
> @Serge,
>
> I might have misready your statement about network config.
> I do add nettwork config (veth0, dev=virbr0, etc) manually.
What do you mean by adding it manually? Have you added it to the
/data/lxc/ubuntu1/config? If there is no 'lxc.network.link'
entry there, then a new network namespace is not created, which
is what you need You should jsut be able to
cat ./ubuntu1-template.con >> /data/lxc/ubuntu1/config
to get something that works.
> There is no /etc/lxc/lxc.conf in my system.
Ah, right, that was introduced with precise.
> The reason I used a config file snipped for lxc-create was
> exactly to get this network virtualization layer into the container config.
Right, it's just that you provided that lxc.conf to lxc-create.
lxc-create copied that to where it wanted that path to go - which
is /var/lib/lxc/ubuntu1/config. lxc-create doesn't look at the
template arguments. It's certainly gross that lxc-create passes
information to the templates over the same channel that users do.
Might be worth talking with upstream about changing that for next
cycle.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925513
Title:
plymouth should not run in container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925513/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
