Docker. You know that I love it. I guess maybe sometimes I love it a little too much because on some of my test servers I have been filling up a lot of GB with new images and containers. All of which hang around indefinitely if you don't clear them. Add to that if you have a continuous integration pipeline that builds a new container every time you do a commit/push and you have an ever growing disk of redundant Docker containers and images.
Making your own containers can be a super useful way of not only understanding more about docker, but also for understanding more about the systems administration of your applications or docker images. Maybe you want a specific container for running configured services on your machine, or maybe you want to look at packaging your entire system inside a docker container to make it super easy to run. In this quick post, I am going to dover making a Dockerfile and also what to write in it so that you can start making your own containers, today!
So, you have successfully installed Docker. Brilliant! Now, what?! Well, the obvious thing to do is to go about running some containers. The Docker documentation suggests that you should pull and run the Hello World container, and although it is small, there are much better things we can do straight away to start to show the power of Docker.
Unless you have been living under a metaphorical rock you will have heard about Docker. But although lots of people have heard of Docker, far fewer are using it day-to-day and even less in production. In this short post, I am going to go over what Docker (and containers are) and how you can start to get up and running with Docker.
More ansible goodness this week. We've been working on a basic playbook to set up the innovatively-named Monit monitoring tool to keep an eye on our webservers and give them a kick up the backside if they're misbehaving.
It's based on a very useful Ansible Galaxy role, pgolm's Monit, which installs and configures the tool. However, the role's documentation doesn't necessarily make it obvious how to get the best from Monit, so here's an example playbook for monitoring PHP, MySQL and Nginx to get things started: