auplink segfaults during docker engine startup

[Piotr Parczewski]

auplink segfault entries can be observed in dmesg and journal after booting machine with docker engine installed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: aufs-tools 1:3.2+20130722-1.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jul 28 12:12:11 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
InstallationDate: Installed on 2016-06-02 (56 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: aufs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mike Magin (mmagin-b)]

I am also experiencing this. Seems like debian already fixed it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777559

If I do not have aufs-tools installed, docker complains:
Jul 21 17:59:25 c7-n2b43-cibuild dockerd[22858]: time="2017-07-21T17:59:25.392652902-06:00" level=warning msg="Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/b716be83f20c98bbb917619fd182c8d4f941ae3ef2dda591320475873a8ebeb0-init: exec: \"auplink\": executable file not found in $PATH"

But if I install aufs-tools, I get cores nearly every time docker has been run.