compiling-containers VS ko

A cool thing about Buildkits LLB is that you can write your own front end to BuildKit. At Earthly, this is sort of a starter task for everyone who joins the team.

My frontend was based on intercal and I don't recommend anyone use it[1].

Buildkit functions a bit like a compiler. I wrote an article once about how it all works. [2]

[1]: https://github.com/adamgordonbell/compiling-containers/tree/...

[2]: https://www.docker.com/blog/compiling-containers-dockerfiles...

Earthly is great (disclosure: work on it)

But also checkout out IckFiles, an Intercal frontend for moby buildkit:

https://github.com/adamgordonbell/compiling-containers/tree/...

Hi, I wrote this, thank you for submitting it. I was trying to teach a bit about compilers and container images at the same time and share some working code examples. The code samples are here and here.

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