rules_gitops
rules_docker
DISCONTINUED
Our great sponsors
rules_gitops | rules_docker | |
---|---|---|
1 | 8 | |
155 | 1,058 | |
2.6% | - | |
4.2 | 0.0 | |
about 1 month ago | 6 months ago | |
Starlark | Starlark | |
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_gitops
-
βYou don't need this overengineered goo for your project.β
> βYou don't need this overengineered goo for your project.β
k8s is probably a great excuse to think how to compose your infrastructure and software in a declarative way - I'm still fascinated by https://demo.kubevious.io/ - It just made "click" when playing with that demo - it's not goo it's a different operating system and a different mindset.
You can do 80% with docker-compose / swarm for small projects but:
If you read HN you are in a huge bubble - gruelsome patched tomcat7 apps on Java8 with 20 properties/ini/xml config files are still popular - hosting things in docker or doing ci/cd is still not mainstream. At least in Europe in the public sector stuff where I was involved.
Sure you can mock it - but the declarative approach is powerful - if you can pull it off to have it across all your infrastructure and code with ci/cd and tests you are fast.
This alone correctly implemented https://github.com/adobe/rules_gitops solves so many problems I can't count the useless meetings we had over any of these bullet points, bazel alone would have solved most major pain points in that project. Just by beeing explizit and declarative.
Don't believe the hype but it's a powerful weapon.
rules_docker
- Ko: Easy Go Containers
-
Crafting container images without Dockerfiles
My company uses Bazel's rules docker to build our images: https://github.com/bazelbuild/rules_docker
They're pretty great and have a lot of the caching and parallelism benefits mentioned in the post for free out of the box, along with determinism (which Docker files don't have because you can run arbitrary shell commands). Our backend stack is also built with Bazel so we get a nice tight integration to build our images that is pretty straightforward.
We've also built some nice tooling around this to automatically put our maven dependencies into different layers using Bazel query and buildozer. Since maven deps don't change often we get a lot of nice caching advantages.
-
Speed boost achievement unlocked on Docker Desktop 4.6 for Mac
Did you mean this one? https://github.com/bazelbuild/rules_docker
I was very interested in this Bazel-based way of building containers but its README page says "it is on minimal life support," which does not inspire confidence. How's your experience using it?
-
Build images within another Docker container
As others have said docker in docker or a separate build server are your best options using docker. You can also use Bazel (which doesn't require the docker daemon) to build docker images which will build deterministic images every time due to not incorporating the timestamp: https://github.com/bazelbuild/rules_docker
-
Evolution of code deployment tools at Mixpanel
There's some BazelCon talks about people doing similar stuff but not actually open sourcing their code.
P.S. if you use rules_docker please feel free to open a PR to add your company to our README: https://github.com/bazelbuild/rules_docker/#adopters
-
Is Docker Dead in the Water?
The docker utility isn't the only way to build and run containers. There's also cri-o, podman, and crun among others for running containers. For building there is podman again, Jib for Java applications, and bazel plus many others. The docker approach of using a client to connect to a daemon required to run as root has turned out to be slow and insecure.
-
Buildpacks vs. Dockerfiles
During the last 3 years I've had the pleasure of using Bazel's rules_docker to generate all my container images (https://github.com/bazelbuild/rules_docker).
In a nutshell, rules_docker is a set of build rules for the Bazel build system (https://bazel.build). What's pretty nice about these rules is that they don't rely on a Docker daemon. They are rules that directly construct image tarballs that you can either load into your local Docker daemon or push to a registry.
What's nice about this approach is that image generation works on any operating system. For example, even on a Mac or Windows system that doesn't have Docker installed, you're able to build Linux containers. They are also fully reproducible, meaning that you often don't need to upload layers when pushing (either because they haven't changed, or because some colleague/CI job already pushed those layers).
I guess rules_docker works fine for a variety of programming languages. I've mainly used it with Go, though.
What are some alternatives?
buildah - A tool that facilitates building OCI images.
kaniko - Build Container Images In Kubernetes
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
jib - π Build container images for your Java applications.
cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface
mixpanel-python - Official Mixpanel Python library.
rules_foreign_cc - Build rules for interfacing with "foreign" (non-Bazel) build systems (CMake, configure-make, GNU Make, boost, ninja, Meson)
rules_nodejs - NodeJS toolchain for Bazel.
kpt - Automate Kubernetes Configuration Editing
kubefed - Kubernetes Cluster Federation
example-bazel-monorepo - πΏπ Example Bazel-ified monorepo, supporting Golang, Java, Python, Scala, and Typescript
otomi-core - Self-hosted DevOps PaaS for Kubernetes