Why should I check my container?

Why would should you check your container? It’s a good question. Surely, if you’ve created the container then you know what’s in it and how it should perform.

However, although one of the benefits of creating a Docker container, for instance, is to create an easy-to-understand environment, one downside is that it can be hard to see what the knock-on effects of changing a Dockerfile base image can be on the container behaviour. This can hide all sorts of problems that can be hard to pin down later.

This can be a common scenario if you are working on an application that is built on a container base image operated by a third party. If the third party carries out updates without your knowledge, the application could suddenly stop working. Comparing like with like can take a really long time when trying to work out which version you were using.

Spot the difference

Ellexus Container Checker will produce a full inventory for your container, which takes a lot of time out of any comparison process. This includes versions used, files required and any other dependencies that you might not have been aware of.

If you implement Container Checker is part of continuous integration, you can catch filesystem changes resulting from a Dockerfile change before finding that the application doesn’t work.

Static vs runtime differences: Ellexus Container Checker gives you extra

Google has recently released a tool for comparing two containers, containerdiff. This looks at the differences between the static contents of the two containers.

Ellexus Container Checker provides something extra by looking at run time differences. The tool from Google will tell you what has changed. Ellexus Container Checker will tell you whether that difference matters.