rules_oci
argocd-springboot-demo2
| rules_oci | argocd-springboot-demo2 | |
|---|---|---|
| 3 | 3 | |
| 229 | 2 | |
| 5.7% | - | |
| 8.9 | 6.6 | |
| 4 days ago | about 1 year ago | |
| Starlark | Smarty | |
| Apache License 2.0 | Apache License 2.0 |
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
-
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
argocd-springboot-demo2
What are some alternatives?
rules_docker - Rules for building and handling Docker images with Bazel
jib - 🏗 Build container images for your Java applications.
ko - Build and deploy Go applications
apko - Build OCI images from APK packages directly without Dockerfile
for-win - Bug reports for Docker Desktop for Windows
podman - Podman: A tool for managing OCI containers and pods.