Support for 3rd party container registries

[wbreza]

Proposal

Optional registry and repository configuration elements within docker

Each container configuration element will allow a registry and repository configurations within the docker options that will allow support for specifying the registry and repository that should be used for the container image when build.

If registry is not specified it will fall back to the AZURE_CONTAINER_REGISTRY_ENDPOINT environment variable specified within the azd environment.

If repository is not specified it will default a convention of {project.name}-{service.name}

ACR registries will be natively support and leverage the current logged in principal. To support 3rd party private registries users will need to ensure they run the docker login command with their credentials commands prior deploying from azd.

These options can be configured at the root of the conatainerapp or within each container depending on the application requirements.

Example

The following example shows how a custom registry can be specified when using container apps. In this example the container would be built and pushed to a private container registry on Docker Hub.

Note

Users would need to ensure they are pre-authenticated into the Docker CLI to allow pushing to private sources.

# azure.yaml

name: my-project
metadata:
  template: my-project@0.0.1-beta
services:
  api:
    project: ./src/api
    language: js
    host: containerapp
    docker: 
      registry: docker.io/wbreza
      repository: my-project
      tag: latest

[spboyer]

there are a few registry providers beyond docker. GitHub, GitLab, Docker, Azure, Google, private registries etc. Need to consider authentication and other variations for providers if we go down this route. Check with containers tooling team on their work for this. @bwateratmsft

[bwateratmsft]

As long as all you need to do is use the Docker CLI to pull / push, auth is just a username + a secret given to the Docker CLI. If you need to browse available images (which is what the Docker extension is doing), auth becomes much more complicated and nearly every registry provider has their own auth story.

[wbreza]

Yes, the initial goal would to continue to use the docker CLI since we already take a dependency on it and users will just need to authenticate outside of azd via docker login ... before calling into azd.