TeamCity comes with Docker Support, implemented as a bundled plugin.
TeamCity-Docker support can run on Mac, Linux, and Windows build agents. It uses the
Since version 2018.2, TeamCity has switched from Oracle Java to OpenJDK 8 (by AdoptOpenJDK). All Docker images have been updated to support OpenJDK.
During the build, the build agent reports the following parameters:
|The Docker CLI version|
|The Docker Compose file version if the Docker Compose build step is used|
|The Docker Engine version|
|The Docker Engine OS platform, can have the |
If you are using the Command Line Build step (and not the TeamCity-provided docker steps), these parameters can be used as agent requirements to ensure your build is run only on the agents with Docker installed.
TeamСity-Docker integration provides the following features which facilitate working with Docker under TeamCity:
TeamCity provides the Docker Wrapper extension for Command Line, Maven, Ant, and Gradle runners. Each of the supported runners has the dedicated Docker settings section.
Docker Disk Space Cleaner is an extension to the Free Disk Space build feature ensuring a certain amount of disk space for a build.
Since 2018.2 TeamCity performs regular clean-up of Docker images, related to TeamCity:
Besides that, TeamCity cleans local Docker Caches using the command:
docker system prune --volumes
docker system prune -a
If TeamCity (for some reason) cannot determine that an image was pushed, a user can send a special Service Message to report this information to the TeamCity server:
##teamcity[dockerMessage type='dockerImage.push' value='<full_image_tag>,size:<size in bytes>,digest:<hash>']
##teamcity[dockerMessage type='dockerImage.push' value='myRegistry/repo-test:17,size:2632,digest:sha256:8dc5a195c3dcdc7c288d16288ff3f9ab1d8a5a230e09afb9c8dc9215e861aa55']