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
In the docker task, when using build command, the cli config is ignored. The task creates its own config.json and overrides the DOCKER_CONFIG variable. This causes the docker CLI to fall back to default settings.
Any settings in %userprofile%\.docker\config.json is then not used (proxy settings, contexts set by the docker context command, etc.).
Using DOCKER_CONTEXT variable then results in an error Failed to initialize: unable to resolve docker endpoint: context "wsl": context not found: open D:\TFS\BuildAgent-Deploy\_work\_temp\DockerConfig_1721664299281\contexts\meta\42bda76ffe7cdbda57c5a588398717abc50e6da7c8ed430e66fdfb99f4563f65\meta.json: The system cannot find the path specified.
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2020 Update 1.2
Operation system
Windows Server 2019
Relevant log output
Starting: d
==============================================================================
Task : Docker
Description : Build or push Docker images, login or logout, start or stop containers, or run a Docker command
Version : 2.181.2
Author : Microsoft Corporation
Help : https://aka.ms/azpipes-docker-tsg
==============================================================================
C:\Windows\system32\docker.exe build -f \\build2\Server_Deploy\Dev\Docker\Dockerfile [REDACTED]
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.45/build?buildargs=[REDACTED]": open //./pipe/docker_engine: The system cannot find the file specified.
##[error]The process 'C:\Windows\system32\docker.exe' failed with exit code 1
Finishing: d
Full task logs with system.debug enabled
No response
Repro steps
- Install docker on Windows Server 2019
- Disable default daemon
- Setup connection to remote daemon using `docker context create test ...`
- Switch context `docker context use test`
- Run any pipeline with any dockerfile, task DockerV2, command build, with containerRegistry
The text was updated successfully, but these errors were encountered:
New issue checklist
Task name
DockerV2
Task version
2.181.2
Issue Description
In the docker task, when using build command, the cli config is ignored. The task creates its own config.json and overrides the DOCKER_CONFIG variable. This causes the docker CLI to fall back to default settings.
Any settings in
%userprofile%\.docker\config.json
is then not used (proxy settings, contexts set by thedocker context
command, etc.).Using DOCKER_CONTEXT variable then results in an error
Failed to initialize: unable to resolve docker endpoint: context "wsl": context not found: open D:\TFS\BuildAgent-Deploy\_work\_temp\DockerConfig_1721664299281\contexts\meta\42bda76ffe7cdbda57c5a588398717abc50e6da7c8ed430e66fdfb99f4563f65\meta.json: The system cannot find the path specified.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2020 Update 1.2
Operation system
Windows Server 2019
Relevant log output
Full task logs with system.debug enabled
No response
Repro steps
The text was updated successfully, but these errors were encountered: