@Henning, At one point we thought a workaround was to have devtmpfs mounted in the container. However that is a bad thing to do as changes in the container's /dev will be reflected in the host's /dev.
So the only workaround right now (until grub is fixed in precise) is to check (with 'mount') which device / is mounted from in the container, and then create that device in the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
