Re: [lxc-users] Determining a container's MAC address

2015-09-01 Thread Andrey Repin
Greetings, Peter Steele! > On 08/31/2015 10:03 PM, Serge Hallyn wrote: >> Right - if you use lxc-create to create the config file, and your >> initial lxc.conf (i.e. /etc/lxc/default.conf or whatever you pass >> as CONF to lxc-create -f CONF) contains something like >> >> lxc.network.hwaddr = 00:1

Re: [lxc-users] Preparing for LXC 1.0.8

2015-09-01 Thread Thomas Müller
I'm happy to help track this down. Like I wrote on the other thread, since 1.1 does not exhibit this bug, it seems like LXC is doing something differently in the 1.1 branch - this could be a workaround or an actual bug fix. Given that the 1.1 branch has another bug related to overlayfs ( https://b

Re: [lxc-users] Setting lxc.network.veth.pair

2015-09-01 Thread Syraxes
On Monday, August 31, 2015, Peter Steele wrote: > On 08/30/2015 03:10 PM, Michael H. Warfield wrote: >> >> I played with this a while back and found that you are severely limited for the name length. Using the container name for that is, sooner or later, going to overflow that limit and possibly g

Re: [lxc-users] Determining a container's MAC address

2015-09-01 Thread Peter Steele
On 09/01/2015 02:06 AM, Andrey Repin wrote: Greetings, Peter Steele! lxc.network.hwaddr = 00:xx:xx:xx:xx:xx Do NOT do this. If you want completely random private MAC's, start with 02:... Ref: http://www.iana.org/assignments/ethernet-numbers/ethernet-numbers.xhtml in my default.conf as well

Re: [lxc-users] Adding a host block device to a container

2015-09-01 Thread Serge Hallyn
Quoting Peter Steele (pwste...@gmail.com): > On 08/31/2015 08:41 PM, Fajar A. Nugraha wrote: > >Nope. lxc.cgroup allows you to create and access the block device, > >but you still need to create the device node yourself. > Fair enough. Then I guess I'll use mknod... FWIW there is a lxc-device comm

[lxc-users] subreddit for lxc

2015-09-01 Thread brian mullan
Didnt' know how many of you were aware that there is a sub-reddit for LXC https://www.reddit.com/r/LXC/ Brian ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] Error on vivid upgrade

2015-09-01 Thread Serge Hallyn
Hi, can you look at https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110 and upload your /var/log/apt/term.log there, as well as output of sudo journalctl -u lxc-net ? Quoting Laurent Ducos (ldu...@biblibre.com): > hello > I have a problem after updating "apt-get upgrade" on ubuntu vivid >

Re: [lxc-users] Error on vivid upgrade

2015-09-01 Thread laurent ducos
Very strange, after server reboot all is ok. 2015-09-01 17:19 GMT+02:00 Serge Hallyn : > Hi, > > can you look at https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110 > and upload your /var/log/apt/term.log there, as well as output of > sudo journalctl -u lxc-net > ? > > Quoting Laurent Duc

Re: [lxc-users] Adding a host block device to a container

2015-09-01 Thread Peter Steele
On 09/01/2015 07:25 AM, Serge Hallyn wrote: FWIW there is a lxc-device command that will do the mknod for you, but it won't be persistent (iirc). Support for making that persistent would be welcome. I think that would come in three small pieces: . have src/lxc/lxc_device optionally save the co

Re: [lxc-users] Determining a container's MAC address

2015-09-01 Thread Andrey Repin
Greetings, Peter Steele! >>> lxc.network.hwaddr = 00:xx:xx:xx:xx:xx > >> Do NOT do this. >> If you want completely random private MAC's, start with 02:... > >> Ref: http://www.iana.org/assignments/ethernet-numbers/ethernet-numbers.xhtml >>> in my default.conf as well and that generated a random

Re: [lxc-users] Determining a container's MAC address

2015-09-01 Thread Peter Steele
On 09/01/2015 08:36 AM, Andrey Repin wrote: If your conf file is missing lxc.network.hwaddr, it was either removed, or a container was not created using standard template. You can add it manually with any suitable value. You are correct, I am not using a standard template. The command I am u

Re: [lxc-users] Error on vivid upgrade

2015-09-01 Thread Serge Hallyn
Yeah, I can't reproduce it myself but this seems not uncommon, so I suspect there is a way to get a system into some unexpected state wrt systemd so that the restart during upgrade doesn't work. Quoting laurent ducos (laurentdu...@gmail.com): > Very strange, after server reboot all is ok. > > >

Re: [lxc-users] Adding a host block device to a container

2015-09-01 Thread Serge Hallyn
Quoting Peter Steele (pwste...@gmail.com): > On 09/01/2015 07:25 AM, Serge Hallyn wrote: > >FWIW there is a lxc-device command that will do the mknod for you, > >but it won't be persistent (iirc). Support for making that > >persistent would be welcome. I think that would come in three small > >pi

Re: [lxc-users] Adding a host block device to a container

2015-09-01 Thread Peter Steele
On 09/01/2015 09:15 AM, Serge Hallyn wrote: In that case that's exactly what templates were meant to do. So while I'd still like to see lxc-device updated to support persistence, you could do what you want by 1. creating a lxc.hook.autodev hook which creates the device you want using mknod,

Re: [lxc-users] Determining a container's MAC address

2015-09-01 Thread Robert Pendell
On Tue, Sep 1, 2015 at 11:59 AM, Peter Steele <...> wrote: > On 09/01/2015 08:36 AM, Andrey Repin wrote: >> >> If your conf file is missing lxc.network.hwaddr, it was either removed, or >> a container was not created using standard template. You can add it manually >> with any suitable value. > > >