Today we're announcing an update to CentOS Atomic Host (version 7.20151001), 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 (672 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 (393 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 (391 MB) and xz compressed (390 MB).
Region Image ID ------ -------- sa-east-1 ami-1b52c506 ap-northeast-1 ami-3428b634 ap-southeast-2 ami-43f2bb79 us-west-2 ami-73eaf043 ap-southeast-1 ami-346f7966 eu-central-1 ami-7ed1d363 eu-west-1 ami-3936034e us-west-1 ami-6d9c5a29 us-east-1 ami-951452f0
96586e03a1a172195eae505be35729c1779e137cd1f8c11a74c7cf94b0663cb2 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2 33d338bb42ef916a40ac89adde9c121c98fbd4220b79985f91b47133310aa537 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2.gz 73184e6f77714472f63a7c944d3252aadc818ac42ae70dd8c2e72e7622e4de95 CentOS-Atomic-Host-7.20151001-GenericCloud.qcow2.xz 4e09f6dfae5024191fec9eab799861d87356a6075956d289dcb31c6b3ec37970 CentOS-Atomic-Host-7.20151001-Installer.iso 92932e9565b8118d7ca7cfbe8e18b6efd53783853cc75dae9ad5566c6e0d9c88 CentOS-Atomic-Host-7.20151001-Vagrant-Libvirt.box 8f626bdafaecb954ae3fab6a8a481da1b3ebb8f7acf6e84cf0b66771a3ac3a65 CentOS-Atomic-Host-7.20151001-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.