Today we're announcing an update to CentOS Atomic Host (version 7.20151118), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. Please note that this release is based on content derived from the upstream 7.1 release.
CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org.
CentOS Atomic Host includes these core component versions:
If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command:
$ sudo atomic host upgrade
The easiest way to consume these images is via the Atlas / Vagrant Cloud setup (see https://atlas.hashicorp.com/centos/boxes/atomic-host). For example, getting the VirtualBox instance up would involve running the following two commands on a machine with vagrant installed:
$ vagrant init centos/atomic-host && vagrant up --provider virtualbox
The installer ISO (673 MB) can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This allows flexibility to control the install using kickstarts and define custom storage, networking and user accounts. This is the recommended process for getting CentOS Atomic Host onto bare metal machines, or to generate your own image sets for custom environments.
The CentOS-Atomic-Host-7-GenericCloud.qcow2 (934 MB) is suitable for use in on-premise and local virtualized environments. We test this on OpenStack, AWS and local Libvirt installs. If your virtualization platform does not provide its own cloud-init metadata source, you can create your own NoCloud iso image. The Generic Cloud image is also available compressed in gz format (408 MB) and xz compressed (323 MB).
cf7c5e67e18a3aaa27d1c6c4710bb9c45a62c80fb5e18a836a2c19758eb3d23e CentOS-Atomic-Host-7.20151101-GenericCloud.qcow2 92cf36f528ae00235ad6eb4ee0d0dd32ccf5f729f2c6c9a99a7471882effecaa CentOS-Atomic-Host-7.20151101-GenericCloud.qcow2.gz 263c1f403c352d31944ca8c814fd241693caa12dbd0656a22cdc3f04ca3ca8d1 CentOS-Atomic-Host-7.20151101-GenericCloud.qcow2.xz dfe0c85efff2972d15224513adc75991aabc48ec8f8ad49dad44f8c51cfb8165 CentOS-Atomic-Host-7.20151101-Installer.iso 139eb88d6a5d1a54ae3900c5643f04c4291194d7b3fccf8309b8961bbd33e4ec CentOS-Atomic-Host-7.20151101-Vagrant-Libvirt.box 63ab56d08cdc75249206ad8a7ee3cdd51a226257c8a74053a72564c3ff3d91a0 CentOS-Atomic-Host-7.20151101-Vagrant-Virtualbox.box
The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them.
The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions.
If you run into any problems with the images or components, feel free to ask on the centos-devel mailing list.
Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.