I ran into the same problem, when using the new 2.0.4.13 image. No problems when using 2.0.1.11 image and updating to 2.0.5.6.