This blog entry collects my experiences trying out the 3 Docker extensions available in the Visual Studio Team Services marketplace.
- Docker Integration (1397 downloads): this extension is provided by Microsoft and enables users to build docker images, run docker images or execute docker commands. This plug-in is very similar to the Jenkins Docker Plugin and to other plug-ins in the sense that you need to provide the connection details of a docker host to run the commands on it. The main difference is that this plug-in allows you to run docker compose files. This type of applications are known as multi-container Docker applications and they can be deployed to an existing cluster in Azure Container Services (ACS). One of the things that I don’t like about this plugin is that it needs a build agent in addition to a Linux host, which seems for me like an overkill.
- Docker build task (162 downloads): This open source plugin offers the same basic functionalities than the Docker Integration plug-in, including the capability to build a Dockerfile and a feature to push images to a docker registry. If you don’t supply SSH connection details the docker commands will be executed locally. Another cool thing about this build task is that provides a docker image for a build agent.
- Container Security (34 downloads): this is a Build Step which scannes and locks down container images. This runs a deep scanning for vulnerabilities. I am not familiar with this tool beyond reading the plugin description but seems like it checks the components and packages referenced by the dockerfile against a data base of vulnerabilities and reports any known vulnerability.
Javier Andrés Cáceres Alvis