Atomic Workstation
The idea of an «Atomic Workstation» is to use the ideas of «Project Atomic» to have a core operating system for a desktop/workstation that updates atomically as a whole. Desktop applications are Flatpaks. Local server application development happens primarily in oc cluster up. We also encourage use of «pet» containers via Docker or related tools.
Current status
See this post for links to an installer ISO.
Advantages
The use of rpm-ostree for the core OS brings fully atomic upgrades. Because rpm-ostree is a hybrid image/package system, it’s also possible to layer RPMs for desktop applications which aren’t yet Flatpaks, and «OS extensions» such as powerline and ykclient.
Moving desktop applications into Flatpak brings stronger isolation, and solves very longstanding issues with using yum/dnf for desktop applications, such as the fact that upgrading deletes the files underneath the running application and often breaks it. (And we don’t want most desktop applications in the base ostree stream, since it’s more for the «base OS» which goes along with a kernel which requires a reboot).
One important note: We are focusing here on Flatpak for isolation — we expect to auto-convert packaged RPMs in Fedora into Flatpak, rather than relying primarily on the «3rd party repository» model.
oc cluster up allows developers to test server applications locally with ease, and then push them to production Kubernetes/OpenShift clusters.
Many developers want random utilities which aren’t server apps or desktop apps, such as ansible for example. We encourage running «pet» containers for these where one uses tools like dnf or pip. We should have a specialized desktop terminal application that makes it easy to create/manage these «pet» containers — similar to virt-manager.
Use cases
Pretty much anything that the normal Workstation is used for. The primary target of the Workstation is different varieties of developer, but the Workstation is also supposed to work for other users such as sysadmins, people who want to play games, or people who only want to use productivity applications.
Work Items
Basics
- An ostree repo/branch for Fedora Workstation, constructed using rpm-ostree; this should be an regular output of the Fedora releng infrastructure
- see http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_redesign
- This will basically replace the «System updates» line in the updates list. Need to figure out where to get metadata
Copyright © 2023 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.
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.
- Google+
- RSS
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.
Team Silverblue
Team Silverblue provides immutable infrastructure for your desktop experience. Team Silverblue
Container Tools
Tools from our team help you create, deploy, manage, and secure containers.
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.
Community News
Fedora Atomic Host Nearing End Of Life
by Dusty Mabe – Thursday 21 November 2019
TL;DR Fedora 29 will be End Of Life soon. With it Fedora Atomic Host will have its last incremental release (based on the Fedora 29 stream). Please move to the Fedora CoreOS preview if you can.
Fedora 28->29 Atomic Host Upgrade Guide
by Dusty Mabe – Wednesday 31 October 2018
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.
Buildah version 1.2 Release Announcement
by Tom Sweeney – Saturday 14 July 2018
Buildah version 1.2 Release Announcement
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.
Announcing the Fedora CoreOS community!
by Dusty Mabe – Wednesday 20 June 2018
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.
Buildah version 1.1 Release Announcement
by Tom Sweeney – Tuesday 12 June 2018
Buildah version 1.1 Release Announcement
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.
Name already in use
fedora-atomic / README.md
- Go to file T
- Go to line L
- Copy path
- Copy permalink
- Open with Desktop
- View raw
- Copy raw contents Copy raw contents
Copy raw contents
Copy raw contents
Fedora Atomic (Host)
Fedora Atomic is a sub-spin of the Cloud product in Fedora that is an implementation of the Atomic Host pattern defined by http://projectatomic.io
Tools and source files
The fedora-atomic-docker-host.json file is the core manifest defining what goes into the host (ostree) content.
The rpm-ostree tool is invoked in two places inside Fedora infrastructure.
First, the release OSTree commits (used to generate pre-release trees) are created by:
The updates trees are generated inside bodhi:
In both case, rpm-ostree makes an OSTree commit from a set of RPM packages, which clients then replicate.
This git repository holds the core manifest file fedora-atomic-docker-host.json that is used for that process.
To run an rpm-ostree compose locally, do something like:
Later tools like rpm-ostree-toolbox will consume this OSTree commit, placing the content into several image types like an installer, a cloud image, a PXE-to-Live image, etc.
Cloud (VM) images are generated inside Koji (using ImageFactory -> Anaconda), using the tree content (note use of the ostreesetup Kickstart verb).
The images are started via the above releng git repository, and a list of Koji tasks can be found here:
Fedora atomic что это
Fedora Atomic is one of the three main variants of Fedora that is an implementation of the Atomic Host pattern defined by Project Atomic.
Tools and source files
The fedora-atomic-host.json file is the core manifest defining what goes into the host (OSTree) content.
The rpm-ostree tool is invoked in two places inside Fedora infrastructure.
First, the release OSTree commits (used to generate pre-release trees) are created by:
The updates trees are generated inside bodhi:
In both case, rpm-ostree makes an OSTree commit from a set of RPM packages, which clients then replicate.
This git repository holds the core manifest file fedora-atomic-host.json that is used for that process.
To run an rpm-ostree compose locally, do something like:
Later tools like rpm-ostree-toolbox will consume this OSTree commit, placing the content into several image types like an installer, a cloud image, a PXE-to-Live image, etc.
Cloud images
Cloud (VM) images are generated inside Koji (using ImageFactory -> Anaconda), using the tree content (note use of the ostreesetup Kickstart verb).
The images are started via the above releng git repository, and a list of Koji tasks can be found here: