Project Atomic is now sunset

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.


The Atomic project aims to build a welcoming and diverse community around the various components needed to compose, deploy and manage Atomic hosts and applications inside.

The Atomic project relies on several open source projects as the building blocks used for the project. For the hosts it relies heavily on Linux kernel features, the systemd system and service manager, OSTree and rpm-ostree for updates, Docker, runc, and CRI-O for application deployment, Kubernetes or OpenShift for orchestration, and of course our two primary Linux distributions, Fedora and CentOS. The Atomic community works toward development of the Atomic project in an inclusive way by contributing to the related upstream projects, solving integration issues in the various distributions being used and developing the specific management tools needed for management and system updates.

Discussions and Meetings

The main project mailing list is the "atomic-devel list", which hosts both development and usage discussions. There's also a low traffic list for announcements. (Please note that the mailing list has no traffic, and is reserved for future use.)

For chat, we use the Freenode IRC servers in the #atomic channel.

The general Atomic community meeting is every two weeks at 16:00 UTC on Mondays on channel #atomic. Please check the atomic-devel list for meeting announcements and agendas.

Several Project Atomic's member projects have public meetings, which you are also encouraged to attend.

  • Fedora Atomic Host and FLIBS: every Wednesday at 16:30 UTC in #fedora-meeting-1.
  • Cockpit: every Monday at 15:00 CET / 06:00 Pacific, in #cockpit.

Report Issues

Before reporting issues, please check in chat or on the mailing list that you've found a new issue. You can also search Server Fault for responses to other users with the same issue.

As Project Atomic covers multiple sub-projects and distributions, where to report issues depends on which distribution or component you're reporting and issue against. In general, it's useful to check on chat or the mailing list where to report things. Here are links to a few of the issue trackers:

Other projects use their issue trackers in their individual git repos, under the Project Atomic organization.

Check the Code Out

Most of the source code for our member projects is hosted under the Project Atomic organization on GitHub. See the GitHub organization for a list of projects. This includes


Project Atomic is an open community seeking contributors from everywhere, and of every type. In addition to many core projects needing Go, C or Python code, we also need:

If you are a programmer, please check out any of the many projects under the Project Atomic organization on GitHub for places to contribute. We accept pull requests and do not require a CLA.

Atomic is a work in progress. Join now and help us to shape its future!