Comment 11 for bug 1436723

Ok, so it seems this isn't fixed after all.

Following the exact steps reported in my original message result in a non-starting container (same error message)