Public bug reported: If ubuntu-fan is installed inside an unprivileged LXD container (both host & container are Ubuntu 16.04), it will break networking:
$ journalctl May 29 23:32:47 sandvich ifup[201]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 M May 29 23:32:47 sandvich ifup[201]: Failed to bring up eth0. May 29 23:32:47 sandvich systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE May 29 23:32:47 sandvich systemd[1]: Failed to start Raise network interfaces. I couldn't find any other indication in the log of why it failed. My networking configuration was configured to get an IP address with DHCPv6. That no longer happened after installation of ubuntu-fan. I ran into this problem when following Stephane Graber's tutorial on nesting Docker inside LXD: https://www.stgraber.org/2016/04/13/lxd-2-0 -docker-in-lxd-712/ It turns out that ubuntu-fan is recommended by docker.io: http://packages.ubuntu.com/xenial/docker.io So a mere "apt-get install docker.io" will also install ubuntu-fan, and then break networking inside my container. Easy to skip ubuntu-fan if you don't need it via "--no-install-recommends" but it's a gotcha if you follow the above tutorial as-is. ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586869 Title: ubuntu-fan breaks networking when installed inside an LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1586869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
