Fedora

Warning This guide is based on an old version of Docker. The instructions you find below may be already removed or changed in the Docker codebase. In my last blog post I explained how to run a Docker installation across multiple hosts. In the comments I was asked if it would be possible to use a DHCP server to assign IPs to the containers. I thought immediately — why not? In fact, assigning IPs using DHCP is a nice way to overcome the IP assignment issue I talked about before. ...

Warning This guide is based on an old version of Docker. The instructions you find below may be already removed or changed in the Docker codebase. In my previous blog post I talked about running the Fedora Cloud images on a local KVM with libvirt. This was not a standalone task, but rather the preparation for this blog post: running Docker containers on multiple hosts attached to the same network. I was asked in the comments on my WildFly cluster based on Docker blog post if it would be possible to run a cluster on multiple hosts. I found a very nice tutorial written by Franck Besnard. I’ve decided to set up a similar environment on my own to see how/if it works. ...

Inspired by Matt’s blog post I’ve decided to make something that is similar but better fits my use case. I plan to do some clustering and routing testing and therefore I need to have similar VMs running side-by-side. These images will be short-lived and I would like to automate as many things I can. Additionally, I found out that the images shipped by Fedora require some changes to work well in my case, for example the default 2GB disk is too small. ...

I had a power mangement issue when running Fedora 19 (and later 20) on my Lenovo ThinkPad 430s. When the battery was low - the laptop just powered off itself, without a clean shutdown or even warning me. As you may guess - this wasn’t something I very happy about. Cause I discovered that it happens when the battery is still at 15%. The system reported at that time still about 40 min of available time. ...

It has been a while since my last blog post about recent Docker changes in Fedora. We’ve done some significant work over the last three weeks. Now it’s time to wrap it up. Docker is available in the repositories Now you can enjoy Docker on your Fedora system by executing just one command: yum install docker-io If you’re on RHEL/CentOS you still need to enable epel-testing repository. This shouldn’t be necessary once the lxc package will be available in stable. ...

Lokesh, the docker-io package maintainer at Fedora, does a damn good job at keeping it up to date. I think it’s a good time to see what changed over the last weeks in the Docker-Fedora world. Why Docker is still not available in Fedora? Simple answer There are some technical issues to overcome :) Longer answer The most important blocker is lack of AUFS support in the kernel (upstream as well as Fedora’s and RHEL’s). Alex Larsson is working on a replacement for AUFS using devicemapper. You can read more about this work in a nice blog post where Alex is covering this area. ...

In my previous blog post I introduced Docker and its Fedora integration. Now it’s time to do some serious (read: useful) stuff. A few years ago I started a project called CirrAS. It’s dead now, but the main idea behind it was to form a cluster of JBoss AS servers in the cloud, without any unnecessary steps. You just launched the instances, they found and connected to each other and the result was a working cluster. Additionally every cluster node registered itself in a front-end instance which worked as a load balancer and monitoring/management (we used RHQ) node. ...

For the last couple of days I have been playing with Docker. Docker is a project that helps you create images and run containers. This sounds like virtualization, but it isn’t. It uses Linux Containers (LXC) under the hood to do all the magic. What kind of magic? Read on. Linux Containers The first question you might ask is: how is Docker/LXC different from virtualization? ...

In April 2013 the JBoss Application Server rename to WildFly was announced at Devoxx. Since then the WildFly team made a couple of Alpha releases. They all start with version 8.0.0 to highlight the fact that WildFly is the successor of JBoss AS. Immediately after the first release of WildFly I’ve started to think about getting it into Fedora. A few days ago I finished upgrading all required components and finally packaged Alpha3 version of WildFly. It’s already available in Rawhide and in Fedora 20 updates-testing repository. ...

JBoss Application Server shipped in Fedora makes it easy to run it as a system service. So far you could launch only the standalone mode, there was no easy way to run it in the domain mode. This is going to change. If you’re not familiar with the operating modes, I highly recommend you reading the introduction to it. In short, in domain mode you can launch more than one server on one host easily. But this is not everything – you get a single entry point for management for all these instances. This means that you can deploy applications one all instances by just executing one command! ...