On 09/03/2014 11:36 AM, Amit Saha wrote:
----- Original Message -----
> From: "Nick Coghlan" <ncoghlan(a)redhat.com>
> To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
> Sent: Monday, September 1, 2014 2:41:29 PM
> Subject: [Beaker-devel] Accessing entire host OS from a container
> From the Docker 1.1 release notes
> * / is now allowed as source of --volumes. This means you can bind-mount
> your whole system in a container if you need to.
> This seems like a potentially useful feature when it comes to running
> test harnesses in a container.
Thanks for sharing. I can see the usefulness for us, obviously. However, I can
imagine containers having their files in /var, /run of the host all over, unless
they are mounted read-only and the process in the container doesn't need to write
Note that the host root wouldn't be mounted as the container root -
those would still be separate. The feature lets you do things like mount
the entire host filesystem inside the container at a different path like
So, for example, we could run beaker-system-scan inside the container,
but chrooted into "/host_root" so it reported back info from the host
filesystem, rather than the container filesystem.
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
HSS Provisioning Architect