4 ms·

First thought was CoreOS seem more mature and polished so why Container-VM? I can run CoreOS on my own servers. Can I run Container-VM on them if GCE doesn't c

• JeanMertz 10y ago
  We booted a fresh GKE 1.4 cluster yesterday to migrate from our old 1.3 cluster. Looking at the machine, it looks like this is a fork(?) of CoreOS: $ grep core /etc/passwd core:x:5000:5000::/home/core:/bin/bash $ cat /etc/os-release BUILD_ID=8820.0.0 NAME="Container-VM Image" GOOGLE_CRASH_ID=Lakitu VERSION_ID=55 BUG_REPORT_URL=https://crbug.com/new PRETTY_NAME="Google Container-VM Image" VERSION=55 GOOGLE_METRICS_PRODUCT_ID=26 HOME_URL="https://cloud.google.com/compute/docs/containers/vm-image/" ID=gci $ toolbox Spawning container core-debian-jessie-backports on /var/lib/toolbox/core-debian-jessie-backports. Press ^] three times within 1s to kill container. If not a direct fork, it certainly uses the same base Chromium OS (which is no surprise) and uses some of the same toolsets that CoreOS uses.
• mikecb 10y ago
  You'd still use core on your own servers, but this has the benefit of tight integration with GCE, like verified boot, as well as the accounts and IAM system (seamless key management). But cloud-init configs work across both.