On Mon, 2016-04-18 at 11:37 -0400, James Bottomley wrote: > > # nsenter --mount=/run/build-container/aarch64 nsenter - > > -user=/dev/fd/3 3</run/build-container/user > > It should work, but for some inexplicable reason it's giving EINVAL. > > # nsenter --mount=/run/build-container/aarch64 3</run/build > -container/user > # ls -l /proc/self/fd > total 0 > lrwx------ 1 root root 64 Apr 18 15:31 0 -> /dev/pts/1 > lrwx------ 1 root root 64 Apr 18 15:31 1 -> /dev/pts/1 > lrwx------ 1 root root 64 Apr 18 15:31 2 -> /dev/pts/1 > lr-x------ 1 root root 64 Apr 18 15:31 3 -> /run/build-container/user > lr-x------ 1 root root 64 Apr 18 15:31 4 -> /proc/10304/fd > # nsenter --user=/proc/self/fd/3 > nsenter: reassociate to namespace 'ns/user' failed: Invalid argument > > I think it's because the fd wasn't properly opened by the shell Actually, just to follow up, this is specifically a problem of the type of container I'm running: it's actually an architecture emulation container, so after I've done the mount namespace enter, I'm running under aarch64 emulation and, apparently, qemu has some problem with the setns system call. This does, however, mean I have to enter both namespaces together ... James -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
