Skip to content

Commit bb45436

Browse files
authored
Update RegistryAuthentication.md
1 parent ffdc3fb commit bb45436

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/RegistryAuthentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Interacting with private container registries requires authenticating with those registries.
44

5-
Docker has established a pattern with this via the [`docker login`](https://docs.docker.com/engine/reference/commandline/login/) command, which is a way of interacting with a Docker config file that contains rules for authenticating with specific registries. This file, and the authentication types it encodes, are supported by Microsoft.Net.Build.Containers for registry authentication. This should ensure that this package works seamlessly with any registry you can `docker pull` from and `docker push`.
5+
Docker has established a pattern with this via the [`docker login`](https://docs.docker.com/engine/reference/commandline/login/) command, which is a way of interacting with a Docker config file that contains rules for authenticating with specific registries. This file, and the authentication types it encodes, are supported by Microsoft.Net.Build.Containers for registry authentication. This should ensure that this package works seamlessly with any registry you can `docker pull` from and `docker push`. This file is normally stored at `~/.docker/config.json`, but it can be specified additionally through the `DOCKER_CONFIG` variable, which points to a directory containing a `config.json` file.
66

77
## Kinds of authentication
88

@@ -30,7 +30,7 @@ The `credsStore` section is a single string property whose value is the name of
3030
In some scenarios the standard Docker authentication mechanism described above just doesn't cut it. This tooling has an additional mechanism for providing credentials to registries: environment variables. If environment variables are used, the credential provide mechanism will not be used at all. The following environment variables are supported:
3131

3232
* SDK_CONTAINER_REGISTRY_UNAME
33-
* This should be the username for the registry. If the password for the registry is a token, then the username should be "<token>".
33+
* This should be the username for the registry. If the password for the registry is a token, then the username should be `"<token>"`.
3434
* SDK_CONTAINER_REGISTRY_PWORD
3535
* This should be the password, token, etc for the registry.
3636

0 commit comments

Comments
 (0)