Not having much success reproducing this on a clean machine. In the mean time, I figured I'd fix my laptop and try to see what changes after a restart:
root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc/ ls: cannot access '/proc/sys/fs/binfmt_misc/': Too many levels of symbolic links root@castiana:~# cat /proc/mounts | grep binfmt systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 root@castiana:~# systemctl restart proc-sys-fs-binfmt_misc.automount root@castiana:~# cat /proc/mounts | grep binfmt systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 root@castiana:~# ls -lh /proc/sys/fs/binfmt_misc/ total 0 -rw-r--r-- 1 root root 0 Mar 11 00:56 python2.7 -rw-r--r-- 1 root root 0 Mar 11 00:56 python3.5 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-aarch64 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-alpha -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-arm -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-armeb -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-cris -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-m68k -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-microblaze -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-mips -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-mips64 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-mips64el -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-mipsel -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-ppc -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-ppc64 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-ppc64abi32 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-ppc64le -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-s390x -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-sh4 -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-sh4eb -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-sparc -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-sparc32plus -rw-r--r-- 1 root root 0 Mar 11 00:56 qemu-sparc64 --w------- 1 root root 0 Mar 11 00:56 register -rw-r--r-- 1 root root 0 Mar 11 00:56 status root@castiana:~# So as far as one can tell from the kernel, nothing changed... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
