Thanks Christian, your suggestion does get the container to start, although it also *does* make the mounted ecryptfs available from within the container. That's not what I originally intended — is there a way to make the host's /home appear as the container's /home *without* the mounted ecryptfs, analogous to the way "mount -o bind" does?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657437 Title: Unprivileged containers run by non-root fail to start if trying to bind-mount a directory that contains a mounted ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1657437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
