Docker build error (HTTP 502) on docker for windows

Docker Desktop
1

Hi together,

I get build errors while building Dockerfiles generally. The process crashes while trying to pull the images (FROM …).

I’m using Docker Desktop for WIndows: 4.34.2

docker info
Client:
 Version:    27.2.0
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.2-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.2-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.13.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
 Containers: 8
  Running: 0
  Paused: 0
  Stopped: 8
 Images: 30
 Server Version: 27.2.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
 Kernel Version: 5.15.167.4-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 7.605GiB
 Name: docker-desktop
 ID: 28e962f8-9efd-4db9-8f79-9f64823f11e0
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=npipe://\\.\pipe\docker_cli
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile

My error message:

docker build --pull --rm -f 'source\Dockerfile' -t 'test:latest' 'source'       
[+] Building 0.4s (3/3) FINISHED                                                 docker:desktop-linux
 => [internal] load build definition from Dockerfile                                     0.0s
 => => transferring dockerfile: 491B                                                             0.0s 
 => CANCELED [internal] load metadata for registry.mycompany.com/mylibrary/dotnet/  0.3s 
 => ERROR [internal] load metadata for registry.mycompany.com/mylibrary/dotnet/sd  0.3s 
------
 > [internal] load metadata for registry.mycompany.com/mylibrary/dotnet/sdk:8.0-alpine: 
------
Dockerfile:2
--------------------
   1 |     # Stage 1
   2 | >>> FROM registry.mycompany.com/mylibrary/dotnet/sdk:8.0-alpine AS builder       
   3 |
   4 |     WORKDIR /src
--------------------
ERROR: failed to solve: registry.mycompany.com/mylibrary/dotnet/sdk:8.0-alpine: failed to resolve source metadata for registry.mycompany.com/mylibrary/dotnet/sdk:8.0-alpine: unexpected status from HEAD request to https://registry.mycompany.com/v2/mylibrary/dotnet/sdk/manifests/8.0-alpine: 502 cannotconnect

docker pull registry.mycompany.com/mylibrary/dotnet/sdk:8.0-alpine works like expected.

Any ideas to solve this problem?

Kind regards
Falk

2

The process does not “crash”, it just exits normally with an error.

It seems your company registry can’t be reached (http status 502), it’s a network issue.

Those issues are the hardest to debug, as they fully depend on your local setup, the network, firewalls, Docker Desktop, WSL.

Can you ping or curl registry.mycompany.com from the same CLI? Did you do the pull from the same CLI?

3

Actually, if it is an HTTP status code, it is not a network issue, at least not between the client and the server that responds to the request. The server logs could tell more about the issue, which the sysadmins of the server could check.