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.
I often get bug reports from users asking why can’t I use `docker` as a non root user, by default?
Docker has the ability to change the group ownership of the /run/docker.socket to have group permission of 660, with the group ownership the docker group. This would allow users added to the docker group to be able to run docker containers without having to execute sudo or su to become root. Sounds great…
Read More »
Video above from Kubernetes 1.0 Launch event at OSCON
In the above video, I attempted to put Red Hat’s container efforts into a bit of context, especially with respect to our history of Linux platform development. Having now watched the above video (they forced me to watch!) I thought it would be good to expound on what I discussed in the video.
Admit it, you’ve read one of the umpteen millions of articles breathlessly talking about the new Docker/Kubernetes/Flannel/CoreOS/whatever hotness and thought to yourself, Wow, is this stuff overhyped.
There is some truth to that knee-jerk reaction, and the buzzworthiness of all things container-related should give one pause - It’s turt^H^H^H^Hcontainers all the way down!
Unless you’ve recently returned from a sabbatical year in a remote monastery with no internet, you know that Containers have arrived, and it’s a whole new world.
I’ll save you five minutes of reading, and 90 minutes of watching Disney’s Alladin and assume you know about containers. If not, take a look at Docker, rkt and the Open Container Project. For bonus points, watch How Docker Didn’t Invent Containers from the First Docker Meetup in my adopted hometown of Brno, Czech Republic. When you’re done singing the fantastic Disney songs, come back. I’ll wait.
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!
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:
<none>:<none> images ?<none>:<none> images when I do docker images -a ?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.