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

Follow us, the Nulecule has moved!

The past weeks have been packed with preparations for Red Hat Summit 2015 and getting Atomic App and the Nulecule Specification into good shape. Now that we have finished that, we put at new release process in place and found a new home for the normative Nulecule Specification documents.

Additionally, the first extension of the Nulecule Specification has been started!

Read More »

What are Docker <none>:<none> images?

The last few days, I have spent some time playing around with Docker’s <none>:<none> images. I’m writing this post to explain how they work, and how they affect docker users. This article will try to address questions like:

  1. What are <none>:<none> images ?
  2. What are dangling images ?
  3. Why do I see a lot of <none>:<none> images when I do docker images -a ?
  4. What is the difference between docker images and docker images -a ?

Before I start answering these questions, let’s take a moment to remember that there are two kinds of <none>:<none> images, the good and the bad.

Read More »

Docker, CentOS 6, and You

Recently, I blogged about docker-on-loopback-storage woes and workarounds – a topic that came up during several conversations I had at last month’s Dockercon. Another frequently-discussed item from the conference involved Docker on CentOS 6, and whether and for how long users can count on running this combination.

Docker and CentOS 6 have never been a terrific fit, which shouldn’t be surprising considering that the version of the Linux kernel that CentOS ships was first released over three years before Docker’s first public release (0.1.0). The OS and kernel version you use matter a great deal, because with Docker, that’s where all your contained processes run.

With a hypervisor such as KVM, it’s not uncommon or problematic for an elder OS to host, through the magic of virtualization, all manner of bleeding-edge software components. In fact, if you’re attached to CentOS 6, virtualization is a solid option for running containers in a more modern, if virtual, host.

Read More »

Project Atomic at ContainerCon

Attending ContainerCon in Seattle this year? Co-located with CloudOpen and LinuxCon, ContainerCon is focused on bringing contributors working with containers, the Linux kernel, and other components together to continue improving the Linux container ecosystem.

As you might expect, there’s quite a few talks on the schedule related to Project Atomic or components important to Atomic (like Kubernetes). Here’s a sample of talks you might want to plan on seeing:

Read More »

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 »

» View older news

Ready to try Atomic?

Get Started