The Docker runner supports the
tag Docker commands.
When creating TeamCity projects/ build configurations from a repository URL, the runner is offered as build step during auto-detection, provided a Dockerfile is present in the VCS repository.
|Select the docker command. Depending on the selected command, the settings below will vary.|
Docker Command Parameters
Depending on the selected source, the settings below will vary. The available options include File, a URL or File content.
|Path to file|
Available if File is selected as the source. Specify the path to the Docker file. The path should be relative to the checkout directory.
|Context folder||Available if File is selected as the source. Specify the context for the docker build. If blank, the enclosing folder for Dockerfile will be used.|
URL to file
|Available if URL is selected as the source. The URL can refer to three kinds of resources: Git repositories, pre-packaged tarball contexts, and plain text files. See Docker documentation for details.|
|File Content:||Available if the file content is selected as the source. You can enter the content of the Dockerfile into the field.|
|Image platform||Select <Any> (default), Linux or Windows.|
Provide a newline-separated list of image name:tag(s)
|Additional arguments for 'build' command||Supply additional arguments to the docker build command. See Docker documentation for details.|
|push||Remove image from agent after push||If selected, TeamCity will remove the image with |
docker rmi at the end of the step
|Image name:tag||Provide a newline-separated list of image name:tag(s)|
|other||Command name||Docker sub-command, like |
tag. For run, use Docker Wrapper
|Working directory|| |
|Additional arguments for the command||Additional arguments that will be passed to the docker command.|