TeamCity On-Premises
 
2020.2
You are viewing the documentation for an earlier version of TeamCity On-Premises.
  1. TeamCity Documentation
  2. Administrator's Guide
  3. Integrating TeamCity with Other Tools
  4. Integrating TeamCity with Docker
  5. Configuring Connections to Docker

Configuring Connections to Docker

Edit page
Last modified: 04 March 2021

A preconfigured Docker connection allows you to:

  • log in to an authenticated registry before running a build / log out after the build;

  • clean up the published images after the build.

tip

This type of connection is a part of the TeamCity-Docker integration toolset. Refer to this page for information on software requirements, supported environments, and other common aspects of this integration.

You can configure a Docker Registry connection on the Project Settings | Connections page. TeamCity supports connections to docker.io (default) or private Docker registries. More than one connection can be added to the project. The connection will be available in all the subprojects and build configurations of the current project.

note

After configuring the Docker Registry connection for a TeamCity project, you need to select it when adding the Docker Support feature to the respective build configuration.

Registry Address Format

By default, https://docker.io is used.

To connect to a registry, use the following format: [http(s)://]hostname:port.

If the protocol is not specified, the connection over https is used by default.

Connecting to Private Cloud Registry

TeamCity supports the Azure container registry storing Docker images. You can authenticate using the Service principal (the principal ID and password are used as the connection credentials) or Admin account.

Amazon Elastic Container Registry (AWS ECR) is supported: specify the AWS region and your AWS Security Credentials when configuring the connection.

Connecting to Insecure Registry

To connect to an insecure registry:

  1. Configure all TeamCity agents where Docker is installed to work with insecure repositories as stated in the Docker documentation. This is sufficient to allow the connection to the private registry over HTTP.

  2. To connect to an insecure registry over HTTPS with a self-signed certificate, in addition to the step above, import the self-signed certificate to the JVM of the TeamCity server as described here. You can consult the Docker documentation on using self-signed certificates.

See also

Administrator's Guide