The Stable channel should be used by production clusters. Versions of Container Linux are battle-tested within the Beta and Alpha channels before being promoted. The current version is Container Linux 1911.4.0.

The Alpha channel closely tracks master and is released frequently. The newest versions of system libraries and utilities will be available for testing. The current version is Container Linux 1995.0.0.

Installing via PXE or ISO image

Container Linux Configs

Container Linux allows you to configure machine parameters, configure networking, launch systemd units on startup, and more via Container Linux Configs. These configs are then transpiled into Ignition configs and given to booting machines. Head over to the docs to learn about the supported features.

This is the human-readable config file. This should not be immediately passed to Container Linux. Learn more.

# This config is meant to be consumed by the config transpiler, which will# generate the corresponding Ignition config. Do not pass this config directly# to instances of Container Linux.etcd:# All options get passed as command line flags to etcd.# Any information inside curly braces comes from the machine at boot time.# vmware isn't currently supported for dynamic data, so we can't use {PRIVATE_IPV4}advertise_client_urls:"http://10.0.0.10:2379"initial_advertise_peer_urls:"http://10.0.0.10:2380"# listen on both the official ports and the legacy ports# legacy ports can be omitted if your application doesn't depend on themlisten_client_urls:"http://0.0.0.0:2379"listen_peer_urls:"http://10.0.0.10:2380"# generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3# specify the initial size of your cluster with ?size=Xdiscovery:"https://discovery.etcd.io/<token>"

This is the raw machine configuration, which is not intended for editing. Learn more. Validate the config here.

VMware Guestinfo interface

Setting Guestinfo options

The VMware guestinfo interface is a mechanism for VM configuration. Guestinfo properties are stored in the VMX file, or in the VMX representation in host memory. These properties are available to the VM at boot time. Within the VMX, the names of these properties are prefixed with guestinfo.. Guestinfo settings can be injected into VMs in one of four ways: