OK, so basically this is due to the usrmerge change, that appears to be driven by Redhat who recommend reinstalls for each new major version. It was adopted by Debian and hence Uyuni and you haven't got a reliable way to apply the merge during the in-place upgrades that you historically supported; but it can randomly break things if you don't apply the usrmerge because packages from maintainers may randomly break things by making invalid assumptions about file deployments, but you won't do any work to fix those packages. You also appear to have failed to really document in the release notes that this is even a thing.
Sounds to me like you and Debian got hoodwinked by Redhat into breaking something that arguably wasn't broken. That said, I do very much appreciate you taking the time to explain it and hopefully this discussion will be useful to others who have docker blow up for them due to the apparmor_parser as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2017594 Title: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker Status in apparmor package in Ubuntu: Confirmed Bug description: There appears to be two copies of apparmor_parser installed by previous versions of the apparmor package, in /sbin and /usr/sbin. When updating the apparmor package to apparmor-2.13.3-7ubuntu5.2, only the /sbin/apparmor_parser executable is updated and the /usr/sbin copy is left unchanged. Being earlier the path, /usr/sbin/apparmor_parser is used by Docker when trying to register the docker-default apparmor profile for containers. The orphaned older executable reports a warning about a new parameter in the parser configuration file in the same package, and that warning breaks the version check that docker runs against that executable on the first line of output. trying to parse the warning while looking for the version number results in the error: docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: strconv.Atoi: parsing "file": invalid syntax. As a workaround, we've been replacing the old version in /usr/sbin with a symlink to the file in /sbin, but the package should be corrected to do appropriate behaviour (either delete the unnecessary(?) copy in /usr/sbin or replace it with a symlink) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2017594/+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
