![]() Since November 1st 2020, Docker Hub introduces download rate limits for public image pulls. #teamcityĬonforming with Docker download rate limits If, for some reason, TeamCity cannot determine that an image has been pushed, a user can send a special service message to report this information to the TeamCity server: In a build step with the enabled Docker Wrapper extension.Ī TeamCity agent tracks Docker images tagged or pulled during the builds (the list of images is stored in the buildAgent/system/docker-used-images.dat file).ĭuring clean-up / freeing disk space, the TeamCity agent tries to remove these images if they have not been used within 3 days (or 1 or 0 days, on subsequent attempts to free the disk space).īesides, TeamCity cleans local Docker Caches using the docker system prune -volumes command. In a Docker or Docker Compose build step, or In a build with the Docker Support build feature, or TeamCity regularly cleans up its related Docker images which were tagged/pulled: Docker Disk Space Cleanerĭocker Disk Space Cleaner is an extension to the Free Disk Space build feature ensuring a necessary amount of disk space for a build. If you are using the Command Line build step (and not the specific Docker steps), these parameters can be used as agent requirements to ensure your build is run only on the agents with Docker installed. The Docker Compose file version, if the Docker Compose build step is used. On macOS, the official Docker support for Mac should be installed for the user running the build agent.ĭuring the build, the build agent can report the following Docker-related parameters: On Windows, the integration works for Linux and Windows container modes. On Linux, the integration will run if the installed Docker is detected. It uses the docker executable on the build agent machine, so it should be runnable by the build agent user. TeamCity Docker Support can run on Windows, Linux, and macOS build agents. ![]() If a build configuration uses the Docker runner or the Docker Wrapper extension, TeamCity automatically adds the agent compatibility requirement for this configuration. Based on the and docker.version variables received from the agents, TeamCity distributes builds that use Docker only between agents with the installed Docker engine. TeamCity periodically checks if Docker is available on active build agents. ![]() To use the Docker Compose build runner, you also need to install Docker Compose. The integration requires Docker to be installed on the build agents. If you want to learn how to run Docker inside a build agent container and read other information about the TeamCity Agent Docker images, read our documentation in Docker Hub. ![]() This page is about TeamCity instruments for integrating builds with Docker. The following article contains information common to these tools. You can learn more details about the listed tools in the dedicated Help articles, linked above. This feature also adds the Docker Info tab of Build Results with the information about the images published to the Docker registry during the build. The Docker Support build feature to automatically sign in to a Docker registry before starting a build. The Docker Wrapper extension to execute build steps inside a Docker container. The Docker Compose build runner to start services with the help of the Docker Compose tool during a build. The Docker build runner to launch Docker commands and create Docker images during a build. TeamCity integration with Docker includes:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |