Bottlerocket: An operating system designed for hosting containers
51–60 of 121 posts
Re: Bottlerocket: An operating system designed for hosting containers
#52A 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...
From the AWS Compliance Shared Responsibility Model: https://aws.amazon.com/compliance/shared-responsibility-mode... Operating system maintenance falls under the Customer responsibility side. With using this new OS, would this responsibility shift back to AWS?
You'd need to look towards providers that specifically take on more responsibility like https://compliantkubernetes.com/ (disclaimer: I have worked at Elastisys, the company behind Compliant Kubernetes).
Re: Bottlerocket: An operating system designed for hosting containers
#53I 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
Speaking of branding, I've some questions: 1. When are services branded as AWS (AWS Fargate) vs Amazon (Amazon DynamoDB)? 2. Is BottleRocket a nod to SkyRocket [0] or a movie of the same name? 3. Why is it called Fargate [1]? [0] https://en.wikipedia.org/wiki/Skyrocket [1] https://youtube.com/watch?v=ye3-gUwu9tI&t=44m28s
On Fargate, you got the answer there.
Re: Bottlerocket: An operating system designed for hosting containers
#54This is somewhat false advertising. This is not an operating system in the sense of being a new kernel. It looks like it's a set of build tools for building a Linux distribution.
Re: Bottlerocket: An operating system designed for hosting containers
#55This is somewhat false advertising. This is not an operating system in the sense of being a new kernel. It looks like it's a set of build tools for building a Linux distribution.
An operating system is not defined only by its kernel. It's kernel + APIs + user land. If one of those components is changed radically, it's indeed a new operating system. That's why Ubuntu and Debian are distinct, even if both are based on Linux.
Re: Bottlerocket: An operating system designed for hosting containers
#56I 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
Speaking of branding, I've some questions: 1. When are services branded as AWS (AWS Fargate) vs Amazon (Amazon DynamoDB)? 2. Is BottleRocket a nod to SkyRocket [0] or a movie of the same name? 3. Why is it called Fargate [1]? [0] https://en.wikipedia.org/wiki/Skyrocket [1] https://youtube.com/watch?v=ye3-gUwu9tI&t=44m28s
Re: Bottlerocket: An operating system designed for hosting containers
#57I 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
Re: Bottlerocket: An operating system designed for hosting containers
#58This is somewhat false advertising. This is not an operating system in the sense of being a new kernel. It looks like it's a set of build tools for building a Linux distribution.
An operating system is not defined only by its kernel. It's kernel + APIs + user land. If one of those components is changed radically, it's indeed a new operating system. That's why Ubuntu and Debian are distinct, even if both are based on Linux.
In the context of software development, if you tell someone you're developing a new operating-system you're probably going to conjure up images of writing a new kernel. If you tell people you're developing a new Linux distro, this is closer to what they'll imagine.
Re: Bottlerocket: An operating system designed for hosting containers
#59Re: Bottlerocket: An operating system designed for hosting containers
#60Opening 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.