Project News

Installing One Big Volume with Overlay2

One of the major benefits of the overlay2 filesystem for Docker is that you no longer need to have a separate storage volume for your Docker containers, images and volumes. This means that you don’t need to try to decide how much free space you need in the root FS as opposed to how much you need for containers; you can just create one big volume to fill up the disk.

Since overlay2 is fairly new, though, we’ve chosen to install a separate Docker volume by default on Fedora 26 Atomic Host. This lets users switch back to devicemapper if they run into some kind of issue with overlay2. However, if you’re installing a new dev system, you might want the ease-of-management of having one big volume.

Read More »

Testing System-Containerized Kubernetes

I’ve blogged here in the past about different ways of running Kubernetes and its dependencies in containers. In that post, I discussed how you could side-step the chicken-and-egg complexities of trying to use Docker to run components on which Docker itself relies by running Flannel and etcd in system containers, which don’t rely on Docker to run.

Recently, I’ve been working on running Kubernetes in system containers, too. Since I was already running etcd and Flannel in system containers, I could save on a bit of storage by having Flannel, etcd, and Kubernetes all share the same image in the ostree-based storage that system containers use.

Read More »

Migrating the Docker Storage Driver to overlay2

On the Project Atomic mailing list, Colin Walters posted a quick set of instructions on how to migrate the Docker storage driver from devicemapper to overlay2 on Fedora Atomic Host.

The overlay2 driver will be the default storage driver in Fedora 26, but you can use it on Fedora 25 Atomic now. To switch storage drivers on an installed system, either before or after you rpm-ostree rebase to Fedora 26, you can use the following procedure.

Read More »

Introducing Minishift - Run OpenShift locally

We are happy to introduce you to Minishift, providing a better user experience than our original Atomic Developer Bundle (ADB). We have shifted our development effort from ADB to Minishift, both to improve user experience, and to address the issues caused by depending on Vagrant. We’ll explain this more in a later blog post.

Minishift is a CLI tool that helps you run OpenShift locally by running a single-node cluster inside a VM. You can try out OpenShift or develop with it, day-to-day, on your local host.

Read More »