lxd/apparmor: Workaround socket handling
lxd/apparmor: Workaround socket handling

It appears that on some kernel at least, the connect operation is
evaluated against the non-dereference path when dealing with a symlink.

Signed-off-by: Stéphane Graber <089afc6d81f66f1168a9849e15660feae286e024@ubuntu.com>

stgraber/lxd,stgraber/lxd,lxc/lxd,lxc/lxd,atxwebs/lxd,hallyn/lxd,stgraber/lxd,stgraber/lxd,hallyn/lxd,lxc/lxd,stgraber/lxd,lxc/lxd,atxwebs/lxd,hallyn/lxd,hallyn/lxd,hallyn/lxd,stgraber/lxd,atxwebs/lxd,atxwebs/lxd,lxc/lxd,stgraber/lxd,lxc/lxd,hallyn/lxd,lxc/lxd