touch-packages team mailing list archive

[Kevin Dalley <1452601@xxxxxxxxxxxxxxxxxx>]

Thanks again.

kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start

dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address
Failed to setup lxc-net.
kevin@awabi:~/tmp$ sudo brctl show
bridge name	bridge id		STP enabled	interfaces
virbr0		8000.52540063031d	yes		virbr0-nic

No luck with starting it.

Here is /etc/default/lxc-net

# This file is auto-generated by lxc.postinst if it does not
# exist.  Customizations will not be overridden.
# Leave USE_LXC_BRIDGE as "true" if you want to use lxcbr0 for your
# containers.  Set to "false" if you'll use virbr0 or another existing
# bridge, or mavlan to your host's NIC.
USE_LXC_BRIDGE="true"
# USE_LXC_BRIDGE="false"

# If you change the LXC_BRIDGE to something other than lxcbr0, then
# you will also need to update your /etc/lxc/default.conf as well as the
# configuration (/var/lib/lxc/<container>/config) for any containers
# already created using the default config to reflect the new bridge
# name.
# If you have the dnsmasq daemon installed, you'll also have to update
# /etc/dnsmasq.d/lxc and restart the system wide dnsmasq daemon.
LXC_BRIDGE="lxcbr0"
LXC_ADDR="10.0.3.1"
LXC_NETMASK="255.255.255.0"
LXC_NETWORK="10.0.3.0/24"
LXC_DHCP_RANGE="10.0.3.2,10.0.3.254"
LXC_DHCP_MAX="253"
# Uncomment the next line if you'd like to use a conf-file for the lxcbr0
# dnsmasq.  For instance, you can use 'dhcp-host=mail1,10.0.3.100' to have
# container 'mail1' always get ip address 10.0.3.100.
#LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf

# Uncomment the next line if you want lxcbr0's dnsmasq to resolve the .lxc
# domain.  You can then add "server=/lxc/10.0.3.1' (or your actual )
# to /etc/dnsmasq.conf, after which 'container1.lxc' will resolve on your
# host.
#LXC_DOMAIN="lxc"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
     Loaded: loaded (/etc/init.d/networking)
    Drop-In: /run/systemd/generator/networking.service.d
             └─50-insserv.conf-$network.conf
          /lib/systemd/system/networking.service.d
             └─systemd.conf
     Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
     Loaded: loaded (/etc/init.d/networking)
    Drop-In: /run/systemd/generator/networking.service.d
             └─50-insserv.conf-$network.conf
          /lib/systemd/system/networking.service.d
             └─systemd.conf
     Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS)
    Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS)
     CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
             ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
             ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
             ├─1109 lockfile-touch /var/lock/ntpdate-ifup
             ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
             ├─1128 lockfile-create /var/lock/ntpdate-ifup
             └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
  ...
      inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions