rules_oci
Bazel rules for building OCI containers (by bazel-contrib)
ko
Build and deploy Go applications (by ko-build)
rules_oci | ko | |
---|---|---|
3 | 28 | |
229 | 7,278 | |
5.7% | 1.4% | |
8.9 | 9.1 | |
4 days ago | 4 days ago | |
Starlark | Go | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rules_oci
Posts with mentions or reviews of rules_oci.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-08.
-
Ko: Easy Go Containers
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!
-
Docker Is Four Things
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
-
Tool to build Docker images
Bazel
ko
Posts with mentions or reviews of ko.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-04.
-
Distroless container images with Apko from Chainguard
Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.
-
What is the most common approach to configure a backend app?
- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile
-
Tool to build Docker images
ko
- how to create container for Kubernetes?
-
Golang Backend in Production
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)
-
How to containerize your Go app in 10 minutes!
Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko
-
Containerd... Do I use Docker to build the container image? I miss the Docker Shim
Here is link number 1 - Previous text "ko"
-
HOWTO: Generate Go based multiarch images the easy way
It depends on your use case, but have you ever tried google/ko?
-
`COPY --chmod` reduced the size of my container image by 35%
If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.
-
`COPY –chmod` reduced the size of my container image by 35%
I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko