Comment 1 for bug 1194547

This would go substancially better with debug logs, but since we pretty much know what's going on...

The issue is that when non-flipped (Ubuntu in a container), NM is unable to figure out the driver and just ignores the interface altogether.

In flipped, it sees the device and correctly identifies the driver, which causes the device to be managed. Then carrier detection appears to cause automatic connections to get started.

Two options: make the device ignored altogether and carry on as before, or perhaps a bit nicer (because then you can ask NM about connection states and stuff), have it not do carrier detection.

I'll test the latter, and go with the former if testing fails.