rules_foreign_cc
rules_docker
Our great sponsors
rules_foreign_cc | rules_docker | |
---|---|---|
3 | 8 | |
638 | 1,058 | |
0.9% | - | |
8.1 | 0.0 | |
7 days ago | 7 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_foreign_cc
-
Using Bazel and Conan for external dependencies
Hello, readline or ncurses can be built using bazel rules foreign cc. Just in case…
-
Listing available 'Make' Variables in Genrule?
To actually answer your question, I searched for "TemplateVariableInfo" in the rules_foreign_cc project (since TemplateVariableInfo is the provider that declares template variables), and there's only one location: toolchains/toolchains.bzl. Reading this, the `toolchains.data.env` variable that's set is coming after a call to `expand_locations_and_make_variables` (from foreign_cc/private/framework.bzl), so without running a debugger I have no idea what's there. It's possible that the rules themselves are confused about this.
- Use bazel rules_foreign_cc with these essential patches
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.
-
Does google use rules_docker internally?
I've seen rules_docker is looking for maintainers here ; Does this mean it doesn't use it that much internally? If so, how do they go about using other services e.g docker-compose for running external services e.g database?
-
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?
examples - Examples for Bazel
buildah - A tool that facilitates building OCI images.
distroless - 🥑 Language focused docker images, minus the operating system.
kaniko - Build Container Images In Kubernetes
bazel-compilation-database - Tool to generate compile_commands.json from the Bazel build system
rules_gitops - This repository contains rules for continuous, GitOps driven Kubernetes deployments.
bazel-central-registry - The central registry of Bazel modules for the Bzlmod external dependency system.
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
bazel_conan_pkg_config
jib - 🏗 Build container images for your Java applications.
bazel_pkg_config - Bazel rules for pkg-config tools.
cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface