41–50 of 121 posts
Earlier quoted context omitted.
Bottlerocket does not package docker. It packages containerd instead for its container runtime.
What is the docker-engine package for then? https://github.com/bottlerocket-os/bottlerocket/tree/develop...
Earlier quoted context omitted.
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...
I 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
mailto:hn@ycombinator.com
I’m here for the puns like updog: https://github.com/bottlerocket-os/bottlerocket/blob/develop...
Glad you're enjoying them! We have a glossary just in case: https://github.com/bottlerocket-os/bottlerocket/blob/develop... (my personal favorite is Laika, the first dog in space and our pre-init binary)
> bork: A setting generator called by sundog to generate the random seed for updog, determining where the host falls in the update order.
I 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
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]?
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...
Operating system maintenance falls under the Customer responsibility side. With using this new OS, would this responsibility shift back to AWS?
Opening 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.
I 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
Disclaimer: I work for AWS, but this is not an official answer. What I said is correct to my best knowledge, but I cannot guarantee its correctness/accuracy.
Earlier quoted context omitted.
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
To answer your first question, AFAIK, standalone services that can be used on their own are prefixed with Amazon (eg S3, EC2, DDB), whereas services that are deeply integrated into AWS ecosystem are prefixed with AWS. Disclaimer: I work for AWS, but this is not an official answer. What I said is correct to my best knowledge, but I cannot guarantee its correctness/accuracy.