You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have the issue, that images are pulled from global docker registry, but not from out internal docker registry (even if we are logged in to the registry). Is seems that BuildImageFromDockerfileAsync needs explicit registry auth information. See also https://docs.docker.com/engine/api/v1.40/#section/Authentication
The text was updated successfully, but these errors were encountered:
jehof
changed the title
BuildImageFromDockerfileAsync is passing AuthConfigs not correctly.
BuildImageFromDockerfileAsync is passing AuthConfigs not as Header X-Registry-Config.
Sep 20, 2019
According to the documentation of the Docker API the AuthConfigs for other registries need to be passed as Header X-Registry-Config (https://docs.docker.com/engine/api/v1.40/#operation/ImageBuild), but they are passed as normal parameters (https://github.com/microsoft/Docker.DotNet/blob/5cb89ed1c8630d8c2077135e4048290076f808f0/src/Docker.DotNet/Endpoints/ImageOperations.cs#L46)
https://github.com/microsoft/Docker.DotNet/blob/5cb89ed1c8630d8c2077135e4048290076f808f0/src/Docker.DotNet/Models/ImageBuildParameters.Generated.cs#L73
We currently have the issue, that images are pulled from global docker registry, but not from out internal docker registry (even if we are logged in to the registry). Is seems that BuildImageFromDockerfileAsync needs explicit registry auth information. See also https://docs.docker.com/engine/api/v1.40/#section/Authentication
The text was updated successfully, but these errors were encountered: