thanks again for reporting this. I simply cannot reproduce this and haven't
found any likely cause. If you can reliably reproduce this in some sort
of cloud instance, i.e. so we could start a digitalocean or amazon instance
with a cloud-init script to set up a bad container, that would be
immensely helpful.
My best guess is still that this is a result of the static host bridge
configuration. Have you been able to reproduce this using the default
lxcbr0?
Hi,
thanks again for reporting this. I simply cannot reproduce this and haven't
found any likely cause. If you can reliably reproduce this in some sort
of cloud instance, i.e. so we could start a digitalocean or amazon instance
with a cloud-init script to set up a bad container, that would be
immensely helpful.
My best guess is still that this is a result of the static host bridge
configuration. Have you been able to reproduce this using the default
lxcbr0?