Tagged: docker

When creating containers, having multiple layers dramatically reduces the time of development. Unfortunately, having a bunch of layers is a bad practice. So how do we reconcile the two? Simple, by compiling the Dockerfiles with docker-optimizer.

If you already have some containerized infrastructure running with docker-compose, or just plain docker containers that are provisioned by a config management tool, you definitely want to switch to Kubernetes. Here's how I did it.

Let's assume you're spinning up pure docker containers in your Kubernetes cluster. Not pods, but docker containers. For example you're using docker.inside in your Jenkins builds, and your Kubernetes is hosting the Jenkins instance. You'll notice that your docker container can't access services in your cluster.

If you want to try Kubernetes locally you're in for a lot of trouble. Installing it requires you to deal with changing apt repos, installing docker, installing kubectl and kubeadm, provisioning, installing networking, configuring the keys for cluster access, etc. Fortunately Ubuntu offers an easier way, via snaps.

The 3rd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.

Here are three important lessons we've learned at GermaniumHQ in optimizing build speeds.

Setting up the infrastructure is simpler with the Selenium Grid that is provisioned by Germanium, and available in Docker. All the regression tests are running against the grid now.