I've got a chroot jail with a bindmount back to / in /etc/fstab. When I reboot the computer, it fails just after udev, when it tries to remount the root filesystem read/write. This appears to be caused by a call to mount Reproducible: Always Steps to Reproduce: 1. Add a bindmount of / to /etc/fstab like so: / /path/to/bind none bind 0 0 2. Reboot the computer. Actual Results: * Remounting root filesystem read/write... * Root filesystem could not be mounted R/W :( [ !! ] Give root password for maintenance (or type Control-D for normal startup): Expected Results: Boot should proceed normally, and a bindmount of / should be created. This appears to be caused by the equivalent of calling: mount -o remount,rw / (which gives the error "mount: /path/to/bind not mounted already, or bad option") instead of: mount -o remount,rw /dev/whatever_root_filesystem_is (which correctly remounts /)
this is a util-linux mount/fstab thing, not a bug in our baselayout (and i dont think really a bug at all) try rearranging the order between the real root and the bind root
