Be very careful with /etc/init.d/networking restart --- this can cause severe instability issues on Ubuntu systems. Some versions have this script modified to prevent the trouble, but some don't. The ifupdown tools should be used to restart specific interfaces instead. I know that's insanely confusing, but it's just the way it is.
The AppArmor problem is the "Failed name lookup - disconnected path" entry. This means that the process is running in a filesystem namespace (perhaps a chroot?) where the filename doesn't actually exist. The usual way forward is to add flags=(attach_disconnected) to the profile, e.g.:
Hello zy,
Be very careful with /etc/init. d/networking restart --- this can cause severe instability issues on Ubuntu systems. Some versions have this script modified to prevent the trouble, but some don't. The ifupdown tools should be used to restart specific interfaces instead. I know that's insanely confusing, but it's just the way it is.
The AppArmor problem is the "Failed name lookup - disconnected path" entry. This means that the process is running in a filesystem namespace (perhaps a chroot?) where the filename doesn't actually exist. The usual way forward is to add flags=( attach_ disconnected) to the profile, e.g.:
/sbin/dhclient flags=( attach_ disconnected) { ...
If that isn't sufficient for you, this may be related to https:/ /bugs.launchpad .net/ubuntu/ +source/ apparmor/ +bug/1408106 -- but I must admit I don't know the details of why overlayfs doesn't work well with AppArmor.
Thanks