Bug#820428: [pkg-lxc-devel] Bug#820428: Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-16 Thread Alfonso
Hi, I've removed 'lxcfs' and 'libpam-cgfs', rebooted, and it fixed it (I've got systemd running on the Debian 8 containers, and they can get ip). Thanks, Alfonso. On 16/04/16 07:14, Evgeni Golov wrote: Hi, On Sat, Apr 16, 2016 at 05:47:44AM -0300, Alfonso wrote: Set hostname to . Failed to

Bug#820428: [pkg-lxc-devel] Bug#820428: Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-16 Thread Evgeni Golov
Hi, On Sat, Apr 16, 2016 at 05:47:44AM -0300, Alfonso wrote: > Set hostname to . > Failed to install release agent, ignoring: No such file or directory > Failed to create root cgroup hierarchy: Invalid argument > Failed to allocate manager object: Invalid argument Yeah, that's systemd not able

Bug#820428: [pkg-lxc-devel] Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-16 Thread Alfonso
I forgot to mention: #lxc-start -F -n prueba3 Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create root cgroup hierarchy: Invalid argument Failed to allocate manager object: Invalid argument Regards, Alfonso. On 16/04/16 03:36, Alfonso wrote:

Bug#820428: [pkg-lxc-devel] Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-16 Thread Alfonso
Hi Evgeni : -not using unprivileged containers -container config: # Distribution configuration lxc.include = /usr/share/lxc/config/debian.common.conf lxc.arch = x86_64 # Container specific configuration lxc.rootfs = /home/lxc/prueba3/rootfs lxc.rootfs.backend = dir lxc.utsname = prueba3 #

Bug#820428: [pkg-lxc-devel] Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-16 Thread Evgeni Golov
Hi Alfonso, On Sat, Apr 16, 2016 at 02:18:18AM -0300, Alfonso wrote: > Hi, I've got a similar issue. I have few Debian 8 containers on development, > and yesterday I've updated my notebook (Debian Sid) and they can't get an > ip. > I've tried with a Debian Wheezy guest, and it works fine. Edited

Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-15 Thread Alfonso
Hi, I've got a similar issue. I have few Debian 8 containers on development, and yesterday I've updated my notebook (Debian Sid) and they can't get an ip. I've tried with a Debian Wheezy guest, and it works fine. Edited /etc/apt/sources.list, and switched from "wheezy" to "jessie", then

Bug#820428: [pkg-lxc-devel] Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-09 Thread Evgeni Golov
Hi Harald, On Fri, Apr 08, 2016 at 12:03:50PM +0200, Harald van der Laan wrote: > when i create a new container with lxc of the latest debian/jessie/amd64 the > is no ipv4 network. > when trying to restart the network (systemctl restart networking.service) it > will give a D-Bus error. >

Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-08 Thread Mattia Rizzolo
control: reassign -1 lxc On Fri, Apr 08, 2016 at 12:03:50PM +0200, Harald van der Laan wrote: > package: lxc image debian/jessie/amd64 reassigning to the correct package, as ↑↑↑ this line got mangled or something. > > when i create a new container with lxc of the latest debian/jessie/amd64

Bug#820428: lxc: debian/jessie/amd64 image ipv4 issue

2016-04-08 Thread Harald van der Laan
package: lxc image debian/jessie/amd64 when i create a new container with lxc of the latest debian/jessie/amd64 the is no ipv4 network. when trying to restart the network (systemctl restart networking.service) it will give a D-Bus error. After inspection D-Bus is not installed and because