The use of tools seems to have exploded in the past few years. Simple web applications take 5 tools just to build and more complex setup are even more prevalent. Add to that that we also end up configuring our tools to better suit our needs and you are faced with a big dependency problem. How do you manage those dependencies? My most recent answer is Docker.
It's not easy for developers and users to use tools
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!
As we have already discussed Docker is a great way to isolate your environment and stop items from crashing into each other. Following on from my last post about running tools from inside a container, we looked at running stuff into your container. Now I am going to have some real life examples.