Deploy and Manage Your Containers in the Next-Generation Container OS

Use immutable infrastructure to deploy and scale your containerized applications. Project Atomic mainly comprises Atomic Host, Team Silverblue, and various container tooling. cloud native platforms.


Atomic Host

Atomic Host provides immutable infrastructure for deploying to hundreds or thousands of servers in your private or public cloud. Available in Fedora Atomic Host, CentOS Atomic Host, and Red Hat Atomic Host editions depending on your platform and support needs.

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

Team Silverblue

Team Silverblue provides immutable infrastructure for your desktop experience. Team Silverblue

Container Registries

You can get your containerized applications from the CentOS Container Pipeline and the Fedora Layered Image Build Service

Trusted container content from the projects you already trust.

Learn more about Fedora Layered Images

Learn more about CentOS Container Pipeline

Community News

Fedora 28->29 Atomic Host Upgrade Guide

Introduction

This week we put out the first release of Fedora 29 Atomic Host. This will be the last major release of Fedora Atomic Host as we prepare for Fedora CoreOS which will be released in Fedora 30.

In this post we’ll quickly list some known issues and then talk about updating an existing Fedora 28 Atomic Host system to Fedora 29. We’ll cover preparing the system for upgrade and performing the upgrade.

Read More »

Buildah version 1.2 Release Announcement

Buildah version 1.2 Release Announcement

buildah logo

We’re pleased to announce the release of Buildah version 1.2 which is now available from GitHub for any Linux distro. We are shipping this release on Fedora, RHEL 7, CentOS and Ubuntu in the near future.

The Buildah project has continued to grow over the past several weeks, welcoming several new contributors to the mix. The highlights of this release are the added ability to control image layers when building an image, CVE’s Fixes, the initial support for user namespace handling and several other enhancements and bug fixes.

Read More »

Announcing the Fedora CoreOS community!

Welcome to Fedora CoreOS

Earlier this year Red Hat acquired CoreOS, Inc.. In the past few months we have been working hard to evaluate the different technologies in the CoreOS Container Linux and Project Atomic spaces. Since Container Linux and Atomic Host overlap in functionality quite a bit we have decided to merge future development of the two projects so that we can combine our efforts and bring two great communities of people together to solve future challenges in the transactional update and container operating system landscape.

Read More »

Buildah version 1.1 Release Announcement

Buildah version 1.1 Release Announcement

buildah logo

We’re pleased to announce the release of Buildah version 1.1 which is now available from GitHub for any Linux distro. We are shipping this release on Fedora, RHEL 7, CentOS and Ubuntu in the near future.

The Buildah project has continued to grow over the past several weeks, welcoming several new contributors to the mix, launching new functionality and creating a number of improvements and bug fixes.

Read More »

How to sneak secrets into your containers, without leaving a trace

Default mounts for all of your containers.

I was presenting OpenShift and really the underlying container technology we are building CRI-O, Buildah and Podman to some customers the other day. After the presentation, one of the customers came over to me and said, the biggest problem they have with their users building containers, was they needed to use certificates in the container in order to access their software repositories. But they did not want the certificates to end up embedded in the containers. I pointed out that Red Hat’s version of Docker allowed you to do volume mounts into containers during a docker build. Also Buildah had the same functionality. But he pointed out that they did not want everyone of their engineers to have to add the volumes, or if they were running a container and wanted to update software and they forgot the volume mount then they could not access the certificates.

Read More »

» View older news

Ready to try Atomic?

Get Started