Today we’re releasing a significant update to the CentOS Atomic Host (version 7.20150908), 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, as an installable ISO image, as a qcow2 image, or as an Amazon Machine Image. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org.
Currently, the CentOS Atomic Host includes these core component versions:
kernel 3.10.0-229
docker 1.7.1-108
kubernetes 1.0.0-0.8.gitb2dafda
etcd 2.0.13-2
flannel 0.2.0-10
cloud-init 0.7.5-10
ostree 2015.6-4
atomic 1.0-108
Upgrading
If you’re running the version of CentOS Atomic Host that shipped in June, you can upgrade to the current image by running the following command:
If you’re currently run the older, test version of the CentOS Atomic Host, or if you’re running any other atomic host (from any distro or release in the past), you can rebase to this released CentOS Atomic Host by running the following two commands :
Images
Vagrant
CentOS-Atomic-Host-7-Vagrant-Libvirt.box (393 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box) (404 MB) are Vagrant boxes for Libvirt and Virtualbox providers.
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:
ISO
The installer ISO (682 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.
QCOW2
The CentOS-Atomic-Host-7-GenericCloud.qcow2 (922 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 (389 MB) and xz compressed (303 MB) formats.
Amazon Machine Images
SHA Sums
Release Cycle
The rebuild image will follow the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they’ll be rebuild and included in new images. After the images are tested by the SIG and deemed ready, they’ll be announced. If you’d like to help with the process, there’s plenty to do!
Getting Involved
CentOS Atomic Host is produced by the CentOS Atomic SIG, based on upstream work from Project Atomic. If you’d like to work on testing images, help with packaging, documentation, or even help define the direction of our monthly release — join us!
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.
Getting Help
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.
The post Announcing a New Release of CentOS Atomic Host is fed from ReadySpace Cloud Servers. Contents strictly belongs to ReadySpace and its respective partners.