Create and Run Applications in Linux Containers

Create your application using Docker containers. Deploy and manage containerized applications on a proven, trusted platform.

Project Atomic introduces Atomic App — an implementation of the Nulecule specification, which lets you manage multi-container applications and orchestration metadata as easily as you manage RPMs.

Learn more!


Atomic App

With Atomic App, you can use existing containers as building blocks for your new application product or project.

Databases, web servers, and other common components are vital parts of applications and services. Utilizing existing containers to provide these core infrastructure components lets you focus more on building the stuff that matters and less time packaging and setting up the common plumbing required.

Learn more about Atomic App

Nulecule /NOO-le-kyul/ (noun)

Nulecule is a made-up word meaning "the mother of all atomic articles". Sounds like "molecule". But different.

Also a specification for applications composed from multiple containers. Check it out on Github below, or read through the Getting Started -guide if you want to know more.

Learn more about Nulecule

Atomic Host

Based on proven technology either from Red Hat Enterprise Linux or the CentOS and Fedora projects, Atomic Host is a lightweight, immutable platform, designed with the sole purpose of running containerized applications.

To balance the need between long-term stability and new features, we are providing different releases of Atomic Host for you to choose from.

Get Started

Community News

Creating a Simple Bare Metal Atomic Host Cluster

Atomic host is a great technology for containerized applications. I like it especially on bare metal machines. In this post I will describe how to setup a simple Do-It-Yourself cluster consisting of three netbooted machines running docker over flannel. Flannel provides a NAT-less private network overlay. Through that network, application containers can easily reach any other containers within the cluster regardless of which machine they run on.

We use three machines called a1, a2, and a3. Let’s designate static IP addresses to them.

  • a1: 192.168.99.51
  • a2: 192.168.99.52
  • a3: 192.168.99.53

We install atomic host OS on these machines via netboot from another host. Let’s call that host boothost. It holds all installation and configuration files. We set up an unattended installation and configuration using kickstart and cloud-init.

Read More »

Friends Don't Let Friends Run Docker on Loopback in Production

I’ve heard negative things about the Fedora|CentOS Docker storage configuration in the past, and while manning the Red Hat booth in San Francisco at DockerCon last week, I spoke to a number of people who’ve experienced these storage issues themselves.

Much of the trouble, I think, boils down to how Docker in Fedora and CentOS have shipped with a storage configuration that optimizes for a convenient getting started experience that can lead to inconvenience down the road.

I’ll cover how to reconfigure your Docker installation w/ better-performing storage, but first, a bit of background:

Read More »

Project Atomic Online Meetup Wednesday

Still wondering what this Atomic stuff is all about? Want a quick primer on Project Atomic?

Join us on Wednesday at 2 p.m. Eastern for a high level introduction to Project Atomic and its components. We’ll look at all the pieces of Atomic, from Atomic Host, to rpm-ostree, the Atomic command (/usr/bin/atomic), Nulecule, and Atomic App.

The event is hosted on BlueJeans, you can view the event using your Browser (a plugin is required for Firefox) or using the BlueJeans app on iOS or Android.

Read More »

Using Volumes with Docker can Cause Problems with SELinux

When using SELinux for controlling processes within a container, you need to make sure any content that gets volume mounted into the container is readable, and potentially writable, depending on the use case.

By default, Docker container processes run with the system_u:system_r:svirt_lxc_net_t:s0 label. The svirt_lxc_net_t type is allowed to read/execute most content under /usr, but it is not allowed to use most other types on the system.

Read More »

» View older news

Ready to try Atomic?

Get Started