rules_docker VS go

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.

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?

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?

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

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

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.

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.

Inspecting builder: dashaun/builder:tiny REMOTE: Description: Tiny base image (bionic build image, distroless-like run image) with buildpacks for Java, Java Native Image and Go Created By: Name: Pack CLI Version: 0.28.0+git-b10e41f.build-3729 Trusted: No Stack: ID: io.paketo.stacks.tiny Lifecycle: Version: 0.15.2 Buildpack APIs: Deprecated: (none) Supported: 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9 Platform APIs: Deprecated: (none) Supported: 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.10 Run Images: index.docker.io/paketobuildpacks/run:tiny-cnb gcr.io/paketo-buildpacks/run:tiny-cnb Buildpacks: ID NAME VERSION HOMEPAGE paketo-buildpacks/apache-tomcat Paketo Buildpack for Apache Tomcat 7.9.1 https://github.com/paketo-buildpacks/apache-tomcat paketo-buildpacks/apache-tomee Paketo Buildpack for Apache Tomee 1.4.0 https://github.com/paketo-buildpacks/apache-tomee paketo-buildpacks/azure-application-insights Paketo Buildpack for Azure Application Insights 5.9.3 https://github.com/paketo-buildpacks/azure-application-insights paketo-buildpacks/bellsoft-liberica Paketo Buildpack for BellSoft Liberica 9.10.1 https://github.com/paketo-buildpacks/bellsoft-liberica paketo-buildpacks/ca-certificates Paketo Buildpack for CA Certificates 3.5.1 https://github.com/paketo-buildpacks/ca-certificates paketo-buildpacks/clojure-tools Paketo Buildpack for Clojure Tools 2.6.1 https://github.com/paketo-buildpacks/clojure-tools paketo-buildpacks/datadog Paketo Buildpack for Datadog 3.1.0 https://github.com/paketo-buildpacks/datadog paketo-buildpacks/dist-zip Paketo Buildpack for DistZip 5.4.0 https://github.com/paketo-buildpacks/dist-zip paketo-buildpacks/encrypt-at-rest Paketo Buildpack for Encrypt-at-Rest 4.3.2 https://github.com/paketo-buildpacks/encrypt-at-rest paketo-buildpacks/environment-variables Paketo Buildpack for Environment Variables 4.4.0 https://github.com/paketo-buildpacks/environment-variables paketo-buildpacks/executable-jar Paketo Buildpack for Executable JAR 6.5.0 https://github.com/paketo-buildpacks/executable-jar paketo-buildpacks/git Paketo Buildpack for Git 1.0.0 https://github.com/paketo-buildpacks/git paketo-buildpacks/go Paketo Buildpack for Go 4.0.0 https://github.com/paketo-buildpacks/go paketo-buildpacks/go-build Paketo Buildpack for Go Build 2.0.7 https://github.com/paketo-buildpacks/go-build paketo-buildpacks/go-dist Paketo Buildpack for Go Distribution 2.2.2 https://github.com/paketo-buildpacks/go-dist paketo-buildpacks/go-mod-vendor Paketo Buildpack for Go Mod Vendor 1.0.6 https://github.com/paketo-buildpacks/go-mod-vendor paketo-buildpacks/google-stackdriver Paketo Buildpack for Google Stackdriver 7.0.0 https://github.com/paketo-buildpacks/google-stackdriver paketo-buildpacks/gradle Paketo Buildpack for Gradle 6.10.0 https://github.com/paketo-buildpacks/gradle paketo-buildpacks/image-labels Paketo Buildpack for Image Labels 4.3.0 https://github.com/paketo-buildpacks/image-labels paketo-buildpacks/jattach Paketo Buildpack for JAttach 1.2.0 https://github.com/paketo-buildpacks/jattach paketo-buildpacks/java Paketo Buildpack for Java 8.1.0 https://paketo.io/docs/howto/java paketo-buildpacks/java-memory-assistant Paketo Buildpack for Java Memory Assistant 1.2.0 https://github.com/paketo-buildpacks/java-memory-assistant paketo-buildpacks/java-native-image Paketo Buildpack for Java Native Image 7.42.0 https://paketo.io/docs/howto/java/#build-an-app-as-a-graalvm-native-image-application paketo-buildpacks/leiningen Paketo Buildpack for Leiningen 4.4.0 https://github.com/paketo-buildpacks/leiningen paketo-buildpacks/liberty Paketo Buildpack for Liberty 3.1.0 https://github.com/paketo-buildpacks/liberty paketo-buildpacks/maven Paketo Buildpack for Maven 6.11.0 https://github.com/paketo-buildpacks/maven paketo-buildpacks/native-image Paketo Buildpack for Native Image 5.6.0 https://github.com/paketo-buildpacks/native-image paketo-buildpacks/procfile Paketo Buildpack for Procfile 5.5.0 https://github.com/paketo-buildpacks/procfile paketo-buildpacks/sbt Paketo Buildpack for SBT 6.9.0 https://github.com/paketo-buildpacks/sbt paketo-buildpacks/spring-boot Paketo Buildpack for Spring Boot 5.20.0 https://github.com/paketo-buildpacks/spring-boot paketo-buildpacks/syft Paketo Buildpack for Syft 1.23.0 https://github.com/paketo-buildpacks/syft paketo-buildpacks/upx Paketo Buildpack for UPX 3.3.0 https://github.com/paketo-buildpacks/upx paketo-buildpacks/watchexec Paketo Buildpack for Watchexec 2.7.0 https://github.com/paketo-buildpacks/watchexec Detection Order: ├ Group #1: │ └ paketo-buildpacks/[email protected] │ └ Group #1: │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ └ paketo-buildpacks/[email protected] (optional) ├ Group #2: │ └ paketo-buildpacks/[email protected] │ └ Group #1: │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ └ paketo-buildpacks/[email protected] (optional) ├ Group #3: │ ├ paketo-buildpacks/[email protected] │ │ └ Group #1: │ │ ├ paketo-buildpacks/[email protected] (optional) │ │ ├ paketo-buildpacks/[email protected] (optional) │ │ ├ paketo-buildpacks/[email protected] │ │ ├ paketo-buildpacks/[email protected] (optional) │ │ ├ paketo-buildpacks/[email protected] │ │ ├ paketo-buildpacks/[email protected] │ │ ├ paketo-buildpacks/[email protected] (optional) │ │ ├ paketo-buildpacks/[email protected] (optional) │ │ └ paketo-buildpacks/[email protected] (optional) │ └ paketo-buildpacks/[email protected] │ └ Group #2: │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] │ ├ paketo-buildpacks/[email protected] (optional) │ ├ paketo-buildpacks/[email protected] (optional) │ └ paketo-buildpacks/[email protected] (optional) └ Group #4: └ paketo-buildpacks/[email protected] LOCAL: (not present)

https://github.com/paketo-buildpacks/go/search?l=shell for example. But the situation on many Dockerfile may not be better I have to admit.