![]() Connecting to Insecure RegistryĬonfigure all TeamCity agents where Docker is installed to work with insecure repositories as stated in the Docker documentation. You can authenticate using the Service principal (the principal ID and password are used as the connection credentials) or Admin account.Īmazon Elastic Container Registry (AWS ECR) is supported: specify the AWS region and your AWS Security Credentials when configuring the connection. TeamCity supports the Azure container registry storing Docker images. If the protocol is not specified, the connection over https is used by default. To connect to a registry, use the following format: hostname:port. The connection will be available in all the subprojects and build configurations of the current project.Īfter configuring the Docker Registry connection for a TeamCity project, you need to select it when adding a Docker Support feature to the respective build configuration. More than one connection can be added to a project. TeamCity supports connections to docker.io (default) or private Docker registries. You can configure a Docker Registry connection on the Project Settings | Connections page. Refer to this page for information on software requirements, supported environments, and other common aspects of this integration. This type of connection is a part of the TeamCity-Docker integration toolset. ![]() Sign in to an authenticated registry before running a build / sign out after the build Ĭlean up the published images after the build. A preconfigured Docker connection allows you to: ![]()
0 Comments
Leave a Reply. |