https://goldmann.pl/ Recent content on Marek Goldmann Hugo -- gohugo.io en-us Wed, 10 Jul 2019 00:00:00 +0000 https://goldmann.pl/blog/2019/07/10/red-hat-and-ibm/ Wed, 10 Jul 2019 00:00:00 +0000 https://goldmann.pl/blog/2019/07/10/red-hat-and-ibm/ There we go — the Red Hat—​IBM merger is now complete: As #RedHat's acquisition by @IBM closes, Red Hat will maintain independence and neutrality to give customers freedom, choice and flexibility. Get the news: https://t.co/ggZWYrT8ut pic.twitter.com/rw6hdvrqv7 — Red Hat, Inc. (@RedHat) 9 lipca 2019 This is a pretty big deal. And I’m not talking about money only. Red Hat — a company as I know it I’m a Red Hatter since over 10 years now. https://goldmann.pl/blog/2018/10/14/hello-im-marek/ Sun, 14 Oct 2018 00:00:00 +0000 https://goldmann.pl/blog/2018/10/14/hello-im-marek/ TL;DR; I’m back! It took a while. We didn’t see each other in long time. Probably too long. So, let me introduce myself again. I’m Marek. Since almost 10 years I work for the same company: Red Hat, in the Middleware part of it. Over that time I was working on various different technologies. Among other things it was: virtualization (KVM, IaaS), Fedora (RPM packaging), Cloud (OpenShift), Middleware (TorqueBox) and more. https://goldmann.pl/blog/2014/09/11/resource-management-in-docker/ Thu, 11 Sep 2014 16:38:00 +0100 https://goldmann.pl/blog/2014/09/11/resource-management-in-docker/ In this blog post I would like to touch on the topic of resource management for Docker containers. It is often unclear how it works and what we can and cannot do. I hope that after reading this blog post resource management will be a bit easier for you to understand. Note I assume that you are running Docker on a systemd enabled operating system. If you are on RHEL/CentOS 7+ or Fedora 19+ this is certainly true. https://goldmann.pl/blog/2014/07/30/runninng-docker-containers-as-systemd-services/ Wed, 30 Jul 2014 15:18:00 +0100 https://goldmann.pl/blog/2014/07/30/runninng-docker-containers-as-systemd-services/ Starting and stopping Docker containers is easy with the docker run and docker {stop|kill} commands. By default, when the Docker daemon is restarted, running containers are also restarted. This is a great feature but sometimes you need more control over the container’s lifecycle. Imagine having a container which is linked to another one. Docker does not provide any way of specifying which container should be started when or what to do if a container dies. https://goldmann.pl/blog/2014/07/23/customizing-the-configuration-of-the-wildfly-docker-image/ Wed, 23 Jul 2014 17:10:00 +0100 https://goldmann.pl/blog/2014/07/23/customizing-the-configuration-of-the-wildfly-docker-image/ Default configuration is a great place to start with a project. We at JBoss try to make our projects (and products too!) usable out-of-box for as many use cases as we can, but there is no way that one configuration could satisfy everyone’s needs. For example, we ship 4 flavors of the standalone.xml configuration file with WildFly since there are so many different deployment scenarios. But this is still not enough. https://goldmann.pl/blog/2014/07/18/logging-with-the-wildfly-docker-image/ Fri, 18 Jul 2014 21:45:00 +0100 https://goldmann.pl/blog/2014/07/18/logging-with-the-wildfly-docker-image/ There are various ways to set up logging for Docker containers. Docker itself has a built-in logs command, you can mount a volume from the host and save the logs there, you can create a different container that would be only responsible for log handling, or set up a logging daemon. Every method has some pros and cons and it is up to you to choose the one that fits best. https://goldmann.pl/blog/2014/07/08/jboss-projects-as-docker-images/ Tue, 08 Jul 2014 16:25:00 +0100 https://goldmann.pl/blog/2014/07/08/jboss-projects-as-docker-images/ I recently announced the availability of the official WildFly Docker image. Since then, our portfolio of images has grown a bit - as of today, we have 8 images. But this is not the end. We want to have a nice collection of JBoss projects shipped as Docker images. Automated builds All of our images are hooked up to automated builds. When we push an update to the repository, a new image will be created and pushed to the global registry. https://goldmann.pl/blog/2014/03/06/creating-a-minimal-wildfly-docker-image/ Thu, 06 Mar 2014 10:40:00 +0100 https://goldmann.pl/blog/2014/03/06/creating-a-minimal-wildfly-docker-image/ 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. https://goldmann.pl/blog/2014/01/30/assigning-ip-addresses-to-docker-containers-via-dhcp/ Thu, 30 Jan 2014 18:30:00 +0100 https://goldmann.pl/blog/2014/01/30/assigning-ip-addresses-to-docker-containers-via-dhcp/ 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. https://goldmann.pl/blog/2014/01/21/connecting-docker-containers-on-multiple-hosts/ Tue, 21 Jan 2014 16:20:00 +0100 https://goldmann.pl/blog/2014/01/21/connecting-docker-containers-on-multiple-hosts/ 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.