Bottlerocket does not package docker. It packages containerd instead for its container runtime.

containerd 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.

What is the docker-engine package for then? https://github.com/bottlerocket-os/bottlerocket/tree/develop...

Sorry, 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...

Ah ok, thanks, still finding my way around.

MCAS was designed to only activate in extreme flight conditions (e.g. AoA being abnormally high). The reason why they decided have MCAS activate even without autopilot can probably be traced to this: https://en.wikipedia.org/wiki/Air_France_Flight_447.

Here's one example on why they might have thought it was necessary: https://en.wikipedia.org/wiki/Air_France_Flight_447