If you too are confused like I was when reading the title, here APK means Alpine Package, instead of Android Package.

this is so nice but unfortunately, we can't use alpine for everything. we tried to use alpine where possible but adopting this mean we complicated our stack a bit (apko for alpine base image and buildkit or kaniko for everything else)

If this is related to musl or DNS, we are planning to add glibc base images which should address those issues.

What's the rest of your stack? Do you need RUN commands, or is it a different package format we could add here?

"Reproducible" is a nice word, but I feel like if the granularity of the contents is "other APKs", then it's not as useful as reproducibility in tools which allow more arbitrary contents.

I know some people don't like seeing it brought up in every thread, but if you're talking about declarative, reproducible, minimal, SBOMs, non-Dockerfile building of OCI images, I think a comparison to Nix would be useful. -- Probably a tool like this is easier to use, and surely quicker; but with this you're restricted to just bunch of existing APKs.

> I know some people don't like seeing it brought up in every thread, but if you're talking about declarative, reproducible, minimal, SBOMs, non-Dockerfile building of OCI images, I think a comparison to Nix would be useful. -- Probably a tool like this is easier to use, and surely quicker; but with this you're restricted to just bunch of existing APKs.

Very true, but their sister tool melange will address that by also creating and building new APKs to package new software. After trying out apko, I am impressed but it is obvious that both tools are still in pretty early-stage development, but apko is impressive from what I've seen so far.

Thanks! They're both only a month or so old, and still moving fast. Please leave some feedback in the repo if you'd like to see anything else!

Disclosure: I work at Chainguard.

Thanks, will do!