Live data from Hacker News

Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

cloud.google.com

1–10 of 12 posts

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#3
This is the image that the instances in a Google Container Engine cluster run. Nice that its getting easier and easier to run a local cluster - for most things it doesn't matter but every so often I'd like to test things in a kube configuration locally before deploying to staging/production.

Edit: at least I'm assuming these are the same images as what they run GKE with due to the same name - can anyone confirm this?

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#4
post #3

This is the image that the instances in a Google Container Engine cluster run. Nice that its getting easier and easier to run a local cluster - for most things it doesn't matter but every so often I'd like to test things in a kube configuration locally before deploying to staging/production. Edit: at least I'm assuming these are the same images as what they run GKE with due to the same name - can anyone confirm this?

As of today, GKE uses the Debian-based ContainerVM: https://cloud.google.com/compute/docs/containers/container_v...

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#5
post #4
post #3

This is the image that the instances in a Google Container Engine cluster run. Nice that its getting easier and easier to run a local cluster - for most things it doesn't matter but every so often I'd like to test things in a kube configuration locally before deploying to staging/production. Edit: at least I'm assuming these are the same images as what they run GKE with due to the same name - can anyone confirm this?

As of today, GKE uses the Debian-based ContainerVM: https://cloud.google.com/compute/docs/containers/container_v...

I believe those images are used to run a 1-node kubernetes cluster, but are not the same as those used by GKE.

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#7
post #4
post #3

This is the image that the instances in a Google Container Engine cluster run. Nice that its getting easier and easier to run a local cluster - for most things it doesn't matter but every so often I'd like to test things in a kube configuration locally before deploying to staging/production. Edit: at least I'm assuming these are the same images as what they run GKE with due to the same name - can anyone confirm this?

As of today, GKE uses the Debian-based ContainerVM: https://cloud.google.com/compute/docs/containers/container_v...

Here's the issue tracking the switch: https://github.com/kubernetes/kubernetes/issues/25276

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#8
post #6

It seems these images use systemd (a nice departure from the init.d scripts used in the previous container_vms images [1]). [1] - https://cloud.google.com/compute/docs/containers/container_v...

That isn't a nice departure. It uselessly bloats the image up, introduces untested code that isn't really production ready, and opens you up to security issues.

Debian sysvinit scripts are well understood, are used in production in Fortune 500 companies, and execute much quicker on boot.

Systemd is a mistake, and no one should be backing that project.

Re: Google Container-VM Image: A Container-Optimized OS Image Based on Chromium OS

#10
post #2

Now it[1] just needs a centralized lock service[2] for safe cluster-wide rolling upgrades! The three release channels are already there, with the Omaha upgrade system. 1: https://coreos.com 2: https://coreos.com/etcd

Probably should link this as well: https://github.com/coreos/locksmith
Post reply on HN