Configuring Connections to Docker
Since TeamCity 2017.2 you can configure a Docker connection in TeamCity if you need Docker support build feature enabling 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.
The Project Settings | Connections page allows you to configure a connection to docker.io (default) or a private Docker registry. 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.
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
Since TeamCity 2017.2.3 , it is possible to get authenticated with an Azure container registry storing Docker images using Service principal(the principal ID and password are used as connection credentials) or Admin account.
Connecting to Insecure Registry
To connect to an insecure registry:
Configure all TeamCity agents where Docker is installed to work with insecure repositories as stated Docker documentation. This is sufficient to allow the connection to the private registry over http.
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.