System @world update failed recently with a conflict between docker and systemd. To be able to keep the system updated, docker was uninstalled. After update, attempt was made to reinstall docker. The attached docker-blocked file shows the blocking reason and also how systemd USE flags are configured. Investigating this issue further showed that the blockage is caused by the following line in the RDEPEND section of the ebuild: !sys-apps/systemd[-cgroup-hybrid(+)] According to the documentation, it causes docker to be a "weak blocker" of systemd when a flag condition is not met. Here is an abstract of the USE Defaults Dependency documentation statement: "Appending a (+) or (-) suffix will indicate whether the absence of the flag from a particular version should indicate its presence or absence." It seems to mean that cgroup-hybrid should be unset. However, "emerge -pv systemd" shows that it is actually unset. So, it is not clear what is going on here... Anyway, a local repository was created and the docker ebuild was copied in there with the offending RDEPEND line deleted. It was then possible to reinstall docker. This is shown in the attached docker-workaround file. After this reinstall, docker appears to be working fine. This issue impacts the docker-19.03.5.ebuild file dated January 25 (2020). Reproducible: Always Steps to Reproduce: 1. System update like with genup from the sakaki-tools repository 2. or attempt to install docker on a systemd gnome wayland system 3. Actual Results: Perform system update with systemd and docker installed or attemps to install docker on a system running with systemd and gnome wayland Expected Results: System update complete or docker installation performed
Created attachment 612896 [details] docker-blocked file
Created attachment 612898 [details] docker-workaround file
Created attachment 612900 [details] emerge-info file
You must enable group-hybrid on systemd because docker has not switched to cgroupv2 yet, this is reasonable blocker and must remain so.
