Public bug reported: In order to efficiently exchange data with a test bed in a container, I make ample use of lxc-start-ephemeral's --bdir option to bind-mount a temp dir from the host into the container. However, we can't use ephemeral in autopkgtest production as that leads to failure of some tests due to bugs in overlayfs/aufs.
The problem is that with lxc-clone and lxc-start there is no counterpart at all for the --bdir option. So to do the equivalent thing, one needs to detect the LXC path (lxc-config lxc.lxcpath), make assumptions about the file layout in the container dir (/rootfs, /config), manually mkdir -p the bind mount path, and add the bind mount to config. This feels like poking around in internals way too much and thus not very future- proof, and it's also a lot of effort: http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=5fbbe3f05f4 Could lxc-clone or lxc-start grow a --bdir option as well, to make this simpler and keep the knowledge of paths and file layouts within LXC itself? ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1304309 Title: Bind mounting for cloned containers is too hard; provide equivalent of lxc-start-ephemeral --bind option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304309/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
