In any case, leaving the system unconfigured (even if it is a container)
properly may be seen as a bad thing. In case of this bug we can assume
the administrator has specified net.ipv6.conf.{all,default}.autoconf=0
prior to starting the container thus disabling autoconfiguration
everywhere so ifupdown failing is a bad thing.
I will add the ifupdown project to the task.
** Also affects: ifupdown
Importance: Undecided
Status: New
** Project changed: ifupdown => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964882
Title:
Static IPv6 configuration fails in lxc guests because of readonly
/proc/sys
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/964882/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
