I've got a branch which would have cloud-init disable accept-ra unless cloud-init has an explicit ipv6 configuration (static or dhcp6). This only affects the solicitation effort, ipv6 link-local is of course, unaffected as is explicit ipv6 configuration. I believe LXD is in a position to know if it has an ipv6 enabled bridge; it could control the template to use a dhcp6 config instead of dhcp (which is ipv4) and not the unconfigured IPV6 RA, which on older releases like Xenial and Trusty won't see without configuration anyhow.
I've got a branch which would have cloud-init disable accept-ra unless cloud-init has an explicit ipv6 configuration (static or dhcp6). This only affects the solicitation effort, ipv6 link-local is of course, unaffected as is explicit ipv6 configuration. I believe LXD is in a position to know if it has an ipv6 enabled bridge; it could control the template to use a dhcp6 config instead of dhcp (which is ipv4) and not the unconfigured IPV6 RA, which on older releases like Xenial and Trusty won't see without configuration anyhow.
https:/ /code.launchpad .net/~raharper/ cloud-init/ +git/cloud- init/+merge/ 339437