The Atomic Host platform is now replaced by CoreOS. Users of Atomic Host are encouraged to join the CoreOS community on the Fedora CoreOS communication channels.
The documentation contained below and throughout this site has been retained for historical purposes, but can no longer be guaranteed to be accurate.
Today we’ve released 0.3.0 of Atomic App! We’ve crossed a few things on our roadmap as well as introduced a brand-new provider; Marathon! For those new to Marathon, it’s a cluster-wide init and control system for services in cgroups or Docker containers, that usually runs on top of Apache Mesos.
The main features of this release are:
Project Atomic is pleased to announce the release of the Atomic Developer Bundle (ADB) 1.5, a Vagrant box that provides a ready-to-use development environment for container applications. With ADB, developers can dive right into producing complex, multi-container applications.
The 1.5 release adds the ability to develop and test using OpenShift Origin v3. The ADB is useful on Microsoft Windows, Apple’s OS X and GNU/Linux distributions. The ADB provides a container development ecosystem that ensures that developers are able to work with Linux containers even if their base operating system does not support it.
The Fedora Project’s Cloud Working Group is pleased to announce the December 15 two-week Fedora Atomic Host is ready to download. Fedora Atomic Host is optimized to run Docker containers and is on a rapid-release cycle to match the pace of Linux container technology. Note that there will be no release on December 29 due to the holiday.
We release the Fedora Atomic Host builds approximately every two weeks in all the supported formats (installable ISO, qcow2, Vagrant Boxes, and EC2 images), with the most up-to-date snapshot of our stack to work with Linux containers.
With Docker 1.10 approaching soon, I wanted to talk about one of the useful new features coming that makes it easier to run containers in read-only mode. Using the new --tmpfs you can run a container as read only, but still use writeable directories for things like /etc, /tmp or /run but discard changes when a container is stopped.
By default, Fedora Atomic images come with cloud-init, which supports customization of various aspects of the running instance, including password for the default user. However, if many users in an organization should have access to the Atomic Host, the local configuration of the instance will not scale and user identities, authentication, and authorization need to be based on external identity management solution.
For IPA (FreeIPA/IdM), Active Directory, or generic LDAP servers, SSSD can serve as an agent providing these services, from user identity lookups and user group membership resolution to access control. With an SSSD container now available, Fedora Atomic Hosts can be deployed in very similar way to normal Fedora.