An updated version of CentOS Atomic Host (version 7.20160404) is now available for download, featuring significant updates to docker (1.9.1) and to the atomic run tool. Version 1.9 of the atomic run tool now includes support for storage backend migration, for downloading and deploying specific atomic tree versions, and for displaying process information from all containers running on a host.
CentOS Atomic Host is 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.
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 (731 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 image allows users to control the install using kickstarts and to define custom storage, networking and user accounts. This is the recommended option for getting CentOS Atomic Host onto bare metal machines, or for generating your own image sets for custom environments.
The CentOS-Atomic-Host-7-GenericCloud.qcow2 (1 GB) image 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.
10e024927636863fd11e9a9427f9b552b6c67661f695f418b1228dda33bc6ed5 CentOS-Atomic-Host-7.1603-GenericCloud.qcow2 00a3c556e11094a996f7e688609158aa6909181d34cc767a26a43e41d39a00a2 CentOS-Atomic-Host-7.1603-GenericCloud.qcow2.gz 1ea638075f41f87751d123cc8cfe8860f6987e009b83d9692161209e2c2ce4af CentOS-Atomic-Host-7.1603-GenericCloud.qcow2.xz 9f7717da7b6813b1b7a1f87c577c8977915a8c350c36fb64b1f26dcc60bf21eb CentOS-Atomic-Host-7.1603-Installer.iso f227bcb447f3de1800faf08e453920fd739330cc942ba331467b2099026477f2 CentOS-Atomic-Host-7.1603-Vagrant-Libvirt.box bc451f55a53e1df83b7556a123a99922ffd867c35eaba2dfc6bfd8aecc748472 CentOS-Atomic-Host-7.1603-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.