Build Inko and idoc containers using Alpine

[yorickpeterse]

These are currently built using Fedora, but Fedora isn't really a "stable" distribution in terms of only providing support for about a year. The fedora-minimal image also has a larger base size (129 MiB) versus Alpine (8.15 MiB). As these containers are typically used for CI and quick testing/demo purposes, reducing the size could be beneficial.

In addition, this means that for our own CI we'd only need two sets of images: a Debian image so we can build GNU toolchains, and an Alpine image for everything else, instead of also needing a Fedora image.

TODO

• Change Inko's Dockerfile to use alpine:3
• Release Inko 0.18.0, which would then use Alpine for the new container
• Update idoc to also use alpine:3 and rebuild the container
• Drop the Fedora container we use for tests

[yorickpeterse]

Per actions/runner#801, GitHub's runners don't handle Alpine containers well on ARM64. This means that if we build such containers, they're basically useless for GitHub. We should probably use a different distribution instead, preferably one that has musl 1.2.5 or newer (for the DNS/TCP fixes).

[yorickpeterse]

Debian 13/Trixie might be an option. It's still in the testing phase but might be good enough, and it has musl 1.2.5 and LLVM 17 and LLVM 18. Unfortunately, its version of rclone is still ancient though (from 2022).

[yorickpeterse]

Another option is to just stick with Fedora. Fedora has musl 1.2.5 since version 39 IIRC. The version of glibc is pretty recent, but I think that should be fine since we don't use any new libc features. Having to upgrade the containers every now and then shouldn't pose an issue either.

[yorickpeterse]

We'll stick with Fedora for the time being.