Noticed with qa-vdb from iwdevtools: ``` VDB: detected possibly incorrect RDEPEND (app-containers/docker-24.0.5) app-arch/xz-utils < dev-db/sqlite:3 < dev-libs/libltdl < net-firewall/iptables < sys-libs/libseccomp < sys-process/procps < > sys-apps/systemd:= ``` docker seem to have an automagic dependency on systemd [0][1]. It also looks like, tangentially, we should be doing `tc-export PKG_CONFIG` in the ebuild [2]. [0] https://github.com/moby/moby/blob/3b04fd10e8311098bd786fa9e86460d15358acca/Makefile#L146 [1] https://github.com/moby/moby/blob/master/hack/make.sh#L87 [2] https://github.com/moby/moby/blob/master/hack/make.sh#L29C8-L29C18
ping...
ping
*** Bug 928055 has been marked as a duplicate of this bug. ***
ping!
In my case when I use openrc, the installed docker binary package depended on systemd. It returned the error /usr/bin/dockerd: error while loading shared libraries: libsystemd.so.0: cannot open shared object file: No such file or directory The solution is to compile from source. Therefore, it seems to me if there is no binary package for openrc it should be ignored by portage
same here, running on openrc and docker binary package requires libsystemd. Now my docker crashes. Have to compile from source for the time beeing
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f90e8d6be0c091a76845e423f93d96ff7f68a8bb commit f90e8d6be0c091a76845e423f93d96ff7f68a8bb Author: William Hubbs <williamh@gentoo.org> AuthorDate: 2024-04-26 05:06:40 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2024-04-26 05:08:38 +0000 app-containers/docker: add 26.1.0 Bug: https://bugs.gentoo.org/914076 Closes: https://bugs.gentoo.org/921624 Signed-off-by: William Hubbs <williamh@gentoo.org> app-containers/docker/Manifest | 1 + app-containers/docker/docker-26.1.0.ebuild | 319 +++++++++++++++++++++++++++++ 2 files changed, 320 insertions(+)
I don't see a build option being passed there which means USE=-systemd wont prevent libsystemd use.
Sam You have absolutly rigth! I check
I don't see a build option for this, but I will check again.
(In reply to William Hubbs from comment #11) > I don't see a build option for this, but I will check again. You'll need to patch one in then ;)
There is definitely a build option, of sorts, for it. ebuild: # build binaries ./hack/make.sh dynbinary || die 'dynbinary failed' In hack/make.sh: if ${PKG_CONFIG} 'libsystemd' 2> /dev/null; then DOCKER_BUILDTAGS+=" journald" fi Unfortunately in classic golang style that means implementing the build yourself or patching the script that calls the script. The options exported before running hack/make/dynbinary don't seem particularly complicated though.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b1bd5d199e46738f80666d4171726fc0941566b7 commit b1bd5d199e46738f80666d4171726fc0941566b7 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2024-04-28 06:57:14 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2024-04-28 06:58:00 +0000 app-containers/docker: Fix automagic systemd dependency This broke the binary packages for half our users. Closes: https://bugs.gentoo.org/914076 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> .../{docker-24.0.5.ebuild => docker-24.0.5-r1.ebuild} | 8 ++++++-- .../{docker-24.0.7.ebuild => docker-24.0.7-r1.ebuild} | 8 ++++++-- .../{docker-26.1.0.ebuild => docker-26.1.0-r1.ebuild} | 3 +++ .../docker/files/docker-24.0.5-automagic-systemd.patch | 13 +++++++++++++ .../docker/files/docker-26.1.0-automagic-systemd.patch | 13 +++++++++++++ 5 files changed, 41 insertions(+), 4 deletions(-)
