CoreOS is intended to be a “new” architecture for servers if I am not mistaken. I may be :-)
CoreOS is intended to be a “new” architecture for servers if I am not mistaken. I may be :-)
There is no package manager. You bring everything else with images and containers. If tools are not found on the distro, you have to get them yourself by starting up an image that contains those tools.
The build system that builds a new release is Gentoo. All the packages that are there gets updated, though the final release does not contain emerge or anything that actually can compile or build anything.
After CoreOS got bought out by Redhat, they started porting over those ideas using the Fedora build system (so Redhat packages, yum, etc).
I think the CoreOS Container OS will live on inside GCP as the customized container os as the default distro used on GKE (managed Kubernetes).
Edit: I see someone mention FlatCar. Neat. I guess that is more of a successor project than the one used in GKE.
I found this interesting. Does anyone have any insights how or why Google ended up choosing CoreoS for their GKE offering?
I am 99% sure that this offering is only similar in nature, not a fork or using any bits from Container Linux
A lot of these concepts and benefits apply when you consider cloud images as opposed to PXE boot images. With CoreOS, there was little difference in configuration with these two patters, if the infrastructure had the same topology you could essentially use the same config (VM or Baremetal).
Google Ventures also invested money in CoreOS at one point.
>"With CoreOS, there was little difference in configuration with these two patters, if the infrastructure had the same topology you could essentially use the same config (VM or Baremetal)"
Also are re "cloud images" VMs then, similar to AMIs in AWS?
Cheers
https://cloud.google.com/container-optimized-os/docs/concept...
As I mentioned in the edit, it looks like FlatCar is a true successor fork.