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.
This year’s Flock to Fedora contributor conference is chock-full of Atomic project work. If you’re interested in Atomic Host, containers, and Kubernetes, you’ll have plenty to do for the whole week in Cape Cod. Sessions will cover maintaining containers, writing docs, the FLIBS build system, building alternate-arch containers, and much more. And if you’re in the Boston area … there’s still time to register!
Read through for a list of sessions.
Since Project Atomic has now spread out across several blogs and websites, this is the second of what will become regular updates on events and posts around the Atomic community. This is also a useful catch-up for anyone who doesn’t have time to backfill on all of the individual blog posts.
This week includes kpod, vagrant-buildah, Fedora Atomic Host, CentOS Atomic Host, Kubernetes containers, and more.
Last week, the CentOS Atomic SIG released an updated version of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host.
The release, which came as part of the monthly CentOS release stream, was a modest one, including only a single glibc bugfix update. The next Atomic Host release will be based on the RHEL 7.4 source code and will include support for overlayfs container storage, among other enhancements.
A new Fedora Atomic Host update is available via an OSTree commit:
Commit: f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
Version: 26.101
In this release we have fixed an issue
with our qcow and vagrant images from the 20170723 release. If you used the qcow
or vagrant images from that release then please make sure you are
following the fedora/26/x86_64/atomic-host ref. See this
Atomic Working Group issue for more details.
Like many other Americans, I am fighting the battle to stay fit and I’m not always winning. Staying fit can also be a problem in the container environment. A common problem people have with building container images with tools like Dockerfile and the run-time-based docker build command is the size of the image, as well as the number of build tools that end up inside of it. Another concern about these unnecessary tools is they can weaken your container by opening potential venues for hackers to take advantage.
A really nice feature about Buildah is you can strengthen your container making it “stronger and more fit”. By finely tuning the creation of the container, and then adding or removing pieces as you desire, you can control the size of your container and lessen its vulnerabilities. It’s all under your control.