[Lxc-users] Bind mount point must be in container root?

[Jäkel, Guido]

Dear Kaj,

You step into a non-trivial trap. It will work either if your mount path inside the container isn't 'mnt' or if you use  lxc.pivotdir  to define it to something other than it default 'mnt'. To get rid of this problem, I'm using an argument like  '-s lxc.pivotdir=$CONTAINER' in my starter script.

With greetings

Guido

>-----Original Message-----
>From: Kaj Wiik [mailto:kaj.wiik at iki.fi]
>Sent: Tuesday, October 08, 2013 12:21 PM
>To: lxc-users at lists.sourceforge.net
>Subject: [Spam-Wahrscheinlichkeit=99][Lxc-users] Bind mount point must be in container root?
>
>Hi!
>
>I noticed that in order to get bind mount (from host to container)
>work, the mount point must be in container root:
>
>This works:
>lxc.mount.entry = /mnt/raid/course_data course_data none bind 0 0
>
>This does not:
>lxc.mount.entry = /mnt/raid/course_data mnt/course_data none bind 0 0
>
>The files just do not show up, no error messages that I could see are emitted...
>
>LXC 0.7.5-3ubuntu67, kernel 3.5.0-41-generic #64~precise1-Ubuntu
>
>Is this expected and documented? Detecting this (and workaround) took
>quite a lot of time...
>
>Cheers,
>Kaj
>
>------------------------------------------------------------------------------
>October Webinars: Code for Performance
>Free Intel webinars can help you accelerate application performance.
>Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>the latest Intel processors and coprocessors. See abstracts and register >
>http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
>_______________________________________________
>Lxc-users mailing list
>Lxc-users at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/lxc-users