New CentOS Atomic Host Ready for Download

Friday , 8, July 2016 3 Comments

An updated version of CentOS Atomic Host (tree version 7.20160707) is now available for download, featuring updated versions of docker (1.10.3) and the atomic run tool (1.10.5). 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:

  • docker-1.10.3-44.el7.centos.x86_64
  • kubernetes-1.2.0-0.12.gita4463d9.el7.x86_64
  • kernel-3.10.0-327.22.2.el7.x86_64
  • atomic-1.10.5-5.el7.x86_64
  • flannel-0.5.3-9.el7.x86_64
  • ostree-2016.5-3.atomic.el7.x86_64
  • etcd-2.2.5-2.el7.0.1.x86_64
  • cloud-init-0.7.5-10.el7.centos.1.x86_64

Upgrading

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

Images

Vagrant

CentOS-Atomic-Host-7-Vagrant-Libvirt.box (467 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (477 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:

$ vagrant init centos/atomic-host && vagrant up --provider virtualbox

ISO

The installer ISO (751 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.

QCOW2

The CentOS-Atomic-Host-7-GenericCloud.qcow2 (1.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.

Amazon Machine Images

Region         Image ID 
------         --------
us-east-1      ami-956fe882 
us-west-2      ami-17569677 
us-west-1      ami-191e5879 
eu-west-1      ami-a06601d3 
eu-central-1   ami-c431dbab 
ap-southeast-1 ami-9638e5f5 
ap-northeast-1 ami-fc867b9d 
ap-southeast-2 ami-6fab800c 
ap-northeast-2 ami-aca369c2 
sa-east-1      ami-30f96d5c

SHA Sums

0eb6fe98706c72635d2f156d3f9cbc4447db3234dafd792ed2b966a562695dcf CentOS-Atomic-Host-7.1606-GenericCloud.qcow2 
3af5dba377f31f52817820f8b940d0490da11d74d01edd70182171f21382fc65 CentOS-Atomic-Host-7.1606-GenericCloud.qcow2.gz 
d28b3f21de85c6c072e277bf873d1657364f6b82f08c91b05ed001ceadb07b79 CentOS-Atomic-Host-7.1606-GenericCloud.qcow2.xz 
ee98acb5a50288e03dc052d4ae5cf0ccbab518f2f15f35500217c90d8088d627 CentOS-Atomic-Host-7.1606-Installer.iso 
43ca397be511a32b3c750a73474039f965d6cc5c7dcfb74846e66366f5d758db CentOS-Atomic-Host-7.1606-Vagrant-Libvirt.box 
d458714f89b1ee3d4e4b7b097877cec9ceec5e651fec9374b4457e5a6c172f3d CentOS-Atomic-Host-7.1606-Vagrant-Virtualbox.box

Release Cycle

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.

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 -- 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.

3 thoughts on “ : New CentOS Atomic Host Ready for Download”
  • Eduard says:

    Nice. Will `atomic host upgrade` make migration of docker storage?

    Docker 1.10 has incompatible data storage format.

  • Jason Brooks says:

    On my test machines with docker 1.9.1 and containers and images, the containers and images remained usable following the atomic host upgrade to docker 1.10.3. I believe that the docker daemon handles conversion on its first startup following the upgrade.

  • Amit says:

    I am unable to use:
    Oracle VBox : Version 5.0.14 r105127
    Vagrant 1.8.5

    D:\vagrant>vagrant init centos/atomic-host && vagrant up
    A `Vagrantfile` has been placed in this directory. You are now
    ready to `vagrant up` your first virtual environment! Please read
    the comments in the Vagrantfile as well as documentation on
    `vagrantup.com` for more information on using Vagrant.
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Box 'centos/atomic-host' could not be found. Attempting to find and
    install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
    The box 'centos/atomic-host' could not be found or
    could not be accessed in the remote catalog. If this is a private
    box on HashiCorp's Atlas, please verify you're logged in via
    `vagrant login`. Also, please double-check the name. The expanded
    URL and error message are shown below:

    URL: ["https://atlas.hashicorp.com/centos/atomic-host"]
    Error:

    -----------------------
    I am not clear on what could be the error. I am connected to internet and able to browse file but using vagrant I am unable to initialize. 🙁 🙁

  • Please give us your valuable comment

    Your email address will not be published. Required fields are marked *