rules_docker VS multipass

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.

Install Multipass from https://multipass.run

Multipass orchestrates virtual Ubuntu instances

Multipass I love Multipass for quick Ubuntu instances spun up for testing or as a playground. Wish I would have known and used of it sooner.

If you just need Ubuntu then you can try "Multipass" from Canonical (https://multipass.run/). Works quite well on my M2 Air. I haven't tried using Linux GUI with it though as I need only terminal based VMs.

Multipass is pretty clutch for trivial VMs on MacOs for sure. I use it for a bunch of ssh jump boxes running vpns to different sites. The macOS build does not support custom images (lest not without [some truly insane hacks](https://github.com/canonical/multipass/issues/1260#issuecomm...) , which doesn’t really matter for what I use it for but it is kind of a bummer. If you need something with a little more grunt but don’t want to go full blown with writing your own QEMU tooling or fussing with something like UTM or Parallels, [quickemu](https://github.com/quickemu-project/quickemu) is a really nice qemu wrapper with sane defaults that can expose a whole lot of power if you need it.

I would be cautious or even distrustful of using anything from Oracle. VirtualBox components come under three different licenses - GPLv2, personal use & evaluation license, and an enterprise license. Their VirtualBox license FAQ [1] gives them enough leeway to change future licenses at will. If an exploit is discovered in your old VirtualBox and they've changed the license, you're out of luck.

We've moved our development to KVM and Virtual Machine Manager on Linux [3] and UTM on Mac [4]. There are other options to run your VM, such as Multipass [5] or VirtualBuddy [6].

On a digressive topic - it was fun migrating our legacy application server stack from Oracle Java (old & poorly considered decision) to OpenJDK, thanks to their license [2].

[1] https://www.virtualbox.org/wiki/Licensing_FAQ

[2] https://www.oracle.com/java/technologies/javase/jdk-faqs.htm...

[3] https://ubuntu.com/blog/kvm-hyphervisor

[4] https://mac.getutm.app/

[5] https://multipass.run/

[6] https://github.com/insidegui/VirtualBuddy

How does it compare to https://multipass.run/?

If you have a reasonably beefy computer, you can always try setting up Multipass and set up 2-3 nodes for a k8s cluster, it's how I'm doing my own certification training. I do have a k3s Raspberry Pi cluster, but with Pi prices being what they are still it'd almost be cheaper to do a cloud setup. ☹️