Docker

The default way of creating an image with Docker is to extend an image by using the FROM call in the Dockerfile. But this is not the only way to do this. You can easily create a base image by using only the yum command. WildFly 8.0.0.Final was recently released and is now available in Fedora 20 updates-testing repository. Let’s create an image that could be used to test this release but make it as minimal as it could be. The application server does have a lot of dependencies, so do not expect a 100 MB image. It’ll be closer to 1 GB. ...

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. ...

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. ...

What and why I am always sad seeing all the potential damage done to your local system, just to set up your development environment. Every time you do almost the same thing, every time you mess your system up in almost the same way. It really doesn’t matter in which language you’re wrtiting and what frameworks you use but Java (and Maven) is a pretty good, uhm, example. A development environment is not only about IDE and JDK, in almost all cases we need to have an application server too. We set it up; our application works great on it, but when we deploy it to production we experience deployment issues. Some things changed: we have different JDK, different network interfaces and so on. Everything can affect your application. ...