3 ms·
> really NOT loving all the over-engineered upstream components like D-Bus and systemd that seem to be there by default. I'm happy with the usage of systemd if
by Conan_Kudo 7y ago
> really NOT loving all the over-engineered upstream components like D-Bus and systemd that seem to be there by default.
I'm happy with the usage of systemd if they take advantage of the hardening features in systemd units for core system services. I'm a bit less happy about the continued usage of Docker, but I get why that's happening for this (EKS and ECS both use it, so it helps support that infrastructure).
- mmzdnp 7y agoBottlerocket does not package docker. It packages containerd instead for its container runtime.
- justincormack 7y agoWhat is the docker-engine package for then? https://github.com/bottlerocket-os/bottlerocket/tree/develop/packages/docker-engine https://github.com/bottlerocket-os/bottlerocket/tree/develop...
- mmzdnp 7y agoSorry, I should have been more clear. The docker packages are there for the development build of Bottlerocket. The Kubernetes variant does not use the docker packages for its build. See more about variants here: https://github.com/bottlerocket-os/bottlerocket/tree/develop/variants https://github.com/bottlerocket-os/bottlerocket/tree/develop...
- justincormack 7y agoAh ok, thanks, still finding my way around.
- Conan_Kudo 7y agocontainerd is the supervisor for the docker/moby container runtime environment. It is not used for crio (for k8s), podman (for non-k8s), or any other OCI container management engine (obviously excluding docker/moby). You obviously know this, but for everyone else playing at home, "Docker" is made up of three distinct projects: moby (CLI and API), containerd (supervisor daemon), and runc (container runtime core). Of the three projects mentioned above, only runc is used by nearly all major "container engines" as people call them. And as pointed out by another poster, you do have the rest in the Bottlerocket tree.