Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bottlerocket: An operating system designed for hosting containers

github.com

Post reply on HN
Print view View original

11–20 of 121 posts

Re: Bottlerocket: An operating system designed for hosting containers

#11

Post by whalesalad »

whalesalad wrote: post #10

A link to the actual source code (90% Rust) and README: https://github.com/bottlerocket-os/bottlerocket And here is a post from AWS with more technical details: https://aws.amazon.com/blogs/aws/bottlerocket-open-source-os...

> To improve security, there's no SSH server in a Bottlerocket image, and not even a shell.

Consider my interest to be piqued.

Re: Bottlerocket: An operating system designed for hosting containers

#12

Post by lysium »

So, the main feature is that updates happen for all packages at once and not for each package individually. Sounds interesting, even for non cloud setups.

How does that work? The explaining image does not explain that. How is that different from rolling back on file system level?

Re: Bottlerocket: An operating system designed for hosting containers

#15

Post by lysium »

whalesalad wrote: post #10

A link to the actual source code (90% Rust) and README: https://github.com/bottlerocket-os/bottlerocket And here is a post from AWS with more technical details: https://aws.amazon.com/blogs/aws/bottlerocket-open-source-os...

Thanks!

I miss the part where it explains how it works. Is it all just containers?

Re: Bottlerocket: An operating system designed for hosting containers

#16

Post by tjkirch »

lysium wrote: post #12

So, the main feature is that updates happen for all packages at once and not for each package individually. Sounds interesting, even for non cloud setups. How does that work? The explaining image does not explain that. How is that different from rolling back on file system level?

The update system is image-based; when an update is downloaded, it's written out to an alternate set of partitions, and then it can flip over to those partitions with a reboot. That makes it easy to roll back with the same kind of single flip, too.

It's different than filesystem-level rollbacks because it's all-or-nothing, so you don't have to worry about update failures after a few packages, and because all of the components in a given image are guaranteed to be tested together, whereas with package-based systems, your combination of packages may have never been used together by anyone else. In addition, for builders, it's easier to sign, distribute, and verify a single image.

Re: Bottlerocket: An operating system designed for hosting containers

#19

Post by geofft »

lysium wrote: post #15
whalesalad wrote: post #10

A link to the actual source code (90% Rust) and README: https://github.com/bottlerocket-os/bottlerocket And here is a post from AWS with more technical details: https://aws.amazon.com/blogs/aws/bottlerocket-open-source-os...

Thanks! I miss the part where it explains how it works. Is it all just containers?

It's buried a bit in the GitHub docs, but it looks like it runs two containerds. One is for Kubernetes. The other is for running administrative containers, including the API server for normal interaction with the host, a server that implements AWS's remote command protocol (enabled by default), and a container that runs sshd (disabled by default).

Packages are built with RPM but RPM isn't used at runtime. Instead, the system is image-based and reboots for updates.

Re: Bottlerocket: An operating system designed for hosting containers

#20

Post by joana035 »

whalesalad wrote: post #10

A link to the actual source code (90% Rust) and README: https://github.com/bottlerocket-os/bottlerocket And here is a post from AWS with more technical details: https://aws.amazon.com/blogs/aws/bottlerocket-open-source-os...

The blog post statements looks like FUD, and of course, are easy to echo.

Is the telemetry enabled by default?

Post reply on HN