ko VS pacoloco

Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.

- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile

ko

You don't need to write and manage Dockerfiles. Simply just use ko: https://github.com/google/ko (You also don't need Docker Engine)

Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko

Here is link number 1 - Previous text "ko"

It depends on your use case, but have you ever tried google/ko?

If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.

I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko

Then there's no man page, and the info available on https://github.com/anatol/pacoloco was confusing to me as well. I think there may be a language interpenetration related barrier at play here.

If you have multiple systems, take a look at pacoloco. It won't save you from having to download the updates once, but after you update one computer, the others sharing the same packages can download from the cache. If you have numerous machines running arch, this will save you a LOT of bandwidth.

Hello, I've just been trying to get pacoloco installed and running on my network, and I seem to have it working with more or less the defaults, but i'm confused about one thing.

The much simpler solution is if you want to save bandwidth, for example if you are installing Arch on a bunch of machines is to either create your own Arch install on removable media (https://wiki.archlinux.org/title/Install_Arch_Linux_on_a_removable_medium) with a local repository with the packages you want (https://wiki.archlinux.org/title/pacman/Tips_and_tricks) or a networked shared pacman cache. I like pacoloco (https://github.com/anatol/pacoloco), but there are others.

Pacoloco https://github.com/anatol/pacoloco might be useful for you

Pacoloco project uses simple and nice way to build images from scratch. See it here https://github.com/anatol/pacoloco/blob/master/Dockerfile

Try https://github.com/anatol/pacoloco pacman cache server and see if you still have these errors. I pretty much sure pacoloco works at RPi.

Parallel download would especially help people who have multiple repos with different speed. e.g. some part of packages is cached locally with pacoloco while other packages need to be fetched via slow high-latency connection.