rules_oci VS ko

rules_docker is deprecated in favor of rules_oci, which also has Rust support: https://github.com/bazel-contrib/rules_oci/blob/main/docs/ru...

I think Bazel can be a good fit for larger polyglot organizations that need to manage large codebases in many languages in a uniform way. Basically Google-circa-2010-sized organizations, coincidentally!

For smaller teams, adopting Bazel too early can be a real productivity drain, where you get all of the downsides of its constraints without as many of their benefits. Bazel is overkill for a project of ~10 Go apps, for example. Ko was actually created to help such a project (Knative) migrate off of Bazel's rules_docker to something better, and I think it achieved the goal!

Not really.

I create my docker images with Bazel/crane [1]. (For reproducibility.)

There is no Dockerfile at all.

[1] https://github.com/bazel-contrib/rules_oci

Bazel

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