mkosi
rules_docker
mkosi | rules_docker | |
---|---|---|
16 | 8 | |
1,043 | 1,058 | |
1.7% | - | |
9.9 | 0.0 | |
6 days ago | 7 months ago | |
Python | Starlark | |
GNU Lesser General Public License v3.0 only | 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.
mkosi
- Build Initramfs Rootless
-
Building minimal GNU/Linux operating system images using Systemd Mkosi
I work with a free and open-source software community called Fedora Project. I had the opportunity to moderate the talk of one of the maintainers of the Systemd suite during the annual contributor conference, Flock To Fedora 2023 where he talked about a tool named Mkosi.
- Mkosi: Build Bespoke OS Images
-
Seamlessly run other Linux distributions inside your terminal
For testing i prefer systemd-nspawn containers with mkosi. A neat tool for running your other fav. distro in a terminal. Works like a charm and integrates nicely in your system. Eg. logs and systemd services or CI testing.
- https://github.com/systemd/mkosi
- man:systemd-nspawn(1)
- man:machinectl(1)
-
Bootable Live USB (Debian)
you're gonna have to build this on an x86 pc. sudo dnf install arch-install-scripts bubblewrap gdisk qemu-user-static rsync systemd-container python3 -m pip install --user git+https://github.com/systemd/mkosi.git git clone https://github.com/leifliddy/asahi-fedora-usb.git cd asahi-fedora-usb
-
LAPAS: The story of how I made a distribution for LanPartyServers
There's also mkosi: https://github.com/systemd/mkosi. This one outputs an iso or similar image file and supports many base distributions.
-
systemd /boot/loader/entries/[entry].conf title default
[1] https://github.com/systemd/mkosi/issues/376
-
Crafting container images without Dockerfiles
System's mkosi is worth checking out too: https://github.com/systemd/mkosi I don't think it generates docker/OCI images directly, but it definitely can generate a tarball of the final image contents and then crane of a similar tool could package it up into an appropriate image. For just docker usage it's probably overkill, the main advantage would be it can build other image types like adding a kernel and init to be a fully bootable iso of VM image.
-
Rocket.Chat🚀+ Constellation💫 = most secure chat server ever (?!)
Constellation ensures that all K8s nodes run on AMD-based Confidential VMs (CVMs). CVMs are strongly isolated from the host and remain encrypted in memory at runtime. Constellation also ensures that all nodes run the same minimal mkosi-based node image.
-
AtomsDevs/Atoms - Easily manage Linux Chroot(s) and Containers
At first glance I thought your project is a frontend for mkosi but then I saw that you support non-systemd targets too. Mentioning it here because it may be relevant to other users/developers.
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?
ostree - Operating system and container binary deployment and upgrades
buildah - A tool that facilitates building OCI images.
efiboots - Manage EFI boot loader entries with this simple GUI
kaniko - Build Container Images In Kubernetes
btdu - sampling disk usage profiler for btrfs
rules_gitops - This repository contains rules for continuous, GitOps driven Kubernetes deployments.
dnfdragora - dnfdragora is a dnf frontend based on libyui abstraction
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
nvidia-auto-installer-for-fedora-linux - A CLI tool which lets you install proprietary NVIDIA drivers and much more easily on Fedora Linux (32 or above and Rawhide)
jib - 🏗 Build container images for your Java applications.
sig-security - 🔐CNCF Security Technical Advisory Group -- secure access, policy control, privacy, auditing, explainability and more!
cri-o - Open Container Initiative-based implementation of Kubernetes Container Runtime Interface