Hi, yes dropping sysvinit completely would help. Just because DISTRO_FEATURES_BACKFILL_CONSIDERED isn't really mandatory according to the docs, so if you have both, this inconsistency will show up.
I don't need both, and thus I'm now using the DISTRO_FEATURES_BACKFILL_CONSIDERED, but figured this was worth mentioning, even if it is a very niche corner case. Thanks Best regards, *Cristóvão Cordeiro* R&D Project Manager *LinkedIn <https://www.linkedin.com/in/cristovaocordeiro/>* *SixSq* *267 Route de Meyrin* *1217 Meyrin* *Geneva* *Switzerland* On Wed, 25 Mar 2020 at 14:09, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > On Wed, Mar 25, 2020 at 7:41 AM Cristóvão Cordeiro > <cristovao.corde...@sixsq.com> wrote: > > > > Dear Bruce, > > > > I've been trying to build docker-ce with the meta-rapsberrrypi layer. > I've appended "systemd" distro to my build. When doing `bitbake docker-ce` > I get an error about > > > > > > update-rc.d: > /home/ubuntu/os-raspberrypi/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-base/1.0-r0/rootfs/etc/init.d/docker.init: > file does not > > > > exist > > > > > > After digging for a bit, I've traced this to the following lines: > > > https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-containers/docker/docker-ce_git.bb?h=zeus#n105 > , where it states that docker.init shall not be installed if systemd in > DISTRO. That's ok. > > > > But then, in > https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-containers/docker/docker.inc?h=zeus#n56 > , INITSCRIPT_NAME is set to docker.init cause sysvinit is also in DISTRO. > > > > Isn't this an inconsistency? Those two conditions should be similar IMO. > The only way to bypass this is to add DISTRO_FEATURES_BACKFILL_CONSIDERED = > "sysvinit" to the build. > > > > Last I checked, you need to have DISTRO_FEATURES_BACKFILL_CONSIDERED = > "sysvinit" to enable systemd. It still is in the example .conf files > that I see in master. But it is possible, I missed a change that it > is no longer required. > > So what you've ended up is with both init systems active at the same > time, and yes, I'm sure that it causing trouble. The check in question > has been there for some time, without issue, so there's definitely > something different in your config than most of the current users > > FWIW: I don't know of many (any) sysvinit users and docker, so I'm > considering dropping the support completely. > > Bruce > > > > Best regards, > > > > Cristovao > > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5234): https://lists.yoctoproject.org/g/meta-virtualization/message/5234 Mute This Topic: https://lists.yoctoproject.org/mt/72538561/21656 Group Owner: meta-virtualization+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
