So it's AWS's version of CoreOS? I wish somebody'd take some VC or R&D money and build distributed computing features into the kernel itself, so we could quit wasting our collective engineering talent, time, money and energy on distributed applications that run on non-distributed-operating-systems. It's like nobody wants to work on creating a round wheel, so instead we're spending all our time building custom roads f…
Bottlerocket: An operating system designed for hosting containers
31–40 of 121 posts
Re: Bottlerocket: An operating system designed for hosting containers
#32Re: Bottlerocket: An operating system designed for hosting containers
#33Their take on using cargo for packaging is quite interesting: https://github.com/bottlerocket-os/bottlerocket/tree/develop...
The cargo.toml workspaces relates more to make IMHO.
Re: Bottlerocket: An operating system designed for hosting containers
#34>It is safe to say that our industry has decided that containers are now the chosen way to package and scale applications.
Curious how the HN community feels about that statement. Not so much about the truth of the statement but about the fact that containers are becoming the de facto method of packaging applications.
Re: Bottlerocket: An operating system designed for hosting containers
#35Fascinating project! Anyone know of possible overlap with Firecracker? Really digging these Rust projects.
Re: Bottlerocket: An operating system designed for hosting containers
#36Re: Bottlerocket: An operating system designed for hosting containers
#37Opening line from their announcement blog post: >It is safe to say that our industry has decided that containers are now the chosen way to package and scale applications. Curious how the HN community feels about that statement. Not so much about the truth of the statement but about the fact that containers are becoming the de facto method of packaging applications.
For load balancers, databases, and other stateful stuff I still run the binaries on VMs.
Re: Bottlerocket: An operating system designed for hosting containers
#38So, 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 c…
Re: Bottlerocket: An operating system designed for hosting containers
#39Earlier quoted context omitted.
> 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).
Bottlerocket does not package docker. It packages containerd instead for its container runtime.
Re: Bottlerocket: An operating system designed for hosting containers
#40I am from AWS. Could we please change the title to say “Bottlerocket from AWS“. Like Firecracker [1] it’s explicitly not AWS branded. 1. https://github.com/firecracker-microvm/firecracker