[Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc

[Stéphane Graber]

I tried starting stopping trusty, wily and xenial containers, none of
that triggers it.

What's odd though is that every report I've seen so far, show no binfmt
mounted, just the autofs. But LXC itself accesses the path so should
have triggered autofs for the previous container startups.

So either this only happens before the first container starts, or
something is unmounting the real binfmt mount.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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