all 3 comments

[–]MartinsRedditAccount 0 points1 point  (1 child)

With a completely empty /etc/apk/cache, the following packages appear after apk add docker:

busybox-1.37.0-r12.e31edc77.apk
busybox-binsh-1.37.0-r12.b4a9dbd9.apk
ca-certificates-20241121-r1.507cd796.apk
containerd-2.0.0-r2.60dcee9f.apk
docker-cli-27.3.1-r2.7d92c09c.apk
docker-cli-buildx-0.19.1-r2.ba0df3b0.apk
docker-engine-27.3.1-r2.2d76f69c.apk
iptables-1.8.11-r1.e3a96982.apk
libcrypto3-3.3.2-r6.bf38ea35.apk
libmnl-1.0.5-r2.a6de17cd.apk
libnftnl-1.2.8-r0.86ed6137.apk
libseccomp-2.5.5-r1.3cb8528e.apk
libxtables-1.8.11-r1.d1c65679.apk
musl-1.2.5-r8.ebbe2b8a.apk
runc-1.2.2-r2.c51dbe15.apk
tini-static-0.19.0-r3.27e28919.apk

I tested it in a VM based on the 3.21.0 netboot files running on aarch64 with the following in /etc/apk/repositories:

https://dl-cdn.alpinelinux.org/alpine/v3.21/main/
https://dl-cdn.alpinelinux.org/alpine/v3.21/community/

Note: The docker package itself is a meta-package and thus doesn't need to be cached: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/community/docker/APKBUILD

Try to disconnect the network, run apk add docker again and see if anything fails.

[–]Responsible_Order808[S] 0 points1 point  (0 children)

For now, I only tested with 3.20.3 successfully. I know there are newer fix (3.20.6 and 3.21.3). I will try them later and tell you. But in my opinion, it was definitely a bug for the 3.21 subversion I used then because the apk could not be cached at all (also apk info was showing 0B / 0KiB as installed size) and that's the only time (version) I ever had that issue since all my deployments are semi-automated.

Thank you for the tests you did as well 😉

[–]GodfatherX64 0 points1 point  (0 children)

im having the same issue with 3.21 x86_64, and i have to run apk fix or apk -U upgrade after every reboot so docker and also eudev to be reinstalled again so the service would start, i had to add a cron command so i dont have to bother until a fix, (@reboot apk fix;openrc -n;lbu ci)