hyperstart: Prevent container rootfs from being mounted readonly
hyperstart: Prevent container rootfs from being mounted readonly

Unfortunately, when mounting the container's rootfs as readonly,
hyperstart cannot properly create the new container because it
cannot create new directories such as /lib/modules for example.

This means that we have to prevent the rootfs from being mounted
as readonly, until we fixed this issue inside hyperstart.

Signed-off-by: Sebastien Boeuf <90b401417360b1924ef3f520ddee932686110f85@intel.com>

containers/virtcontainers,containers/virtcontainers