docker / buildx

Docker CLI plugin for extended build capabilities with BuildKit
Apache License 2.0
3.58k stars 482 forks source link

Authentication not working only in buildx #2749

Open 100tomer opened 1 month ago

100tomer commented 1 month ago

Contributing guidelines

I've found a bug and checked that ...

Description

Hi! I'm running docker login followed by a build with Buildx. The login to the private repository uses a JWT authorization header, and it works perfectly with a standard docker push. However, for some reason, Buildx isn't sending the token from the Docker login to the repository. I've spent hours searching online but haven't found a solution yet.

Expected behaviour

I expect the docker buildx to send the token in the request headers like normal docker push

Actual behaviour

not sending

Buildx version

github.com/docker/buildx v0.16.2-desktop.1 081c21b9e461293ae243a1ff813a680a4f5f8fb9

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: /Users//.docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.29.2-desktop.2 Path: /Users//.docker/cli-plugins/docker-compose debug: Get a shell into any image or container (Docker Inc.) Version: 0.0.34 Path: /Users//.docker/cli-plugins/docker-debug desktop: Docker Desktop commands (Alpha) (Docker Inc.) Version: v0.0.15 Path: /Users//.docker/cli-plugins/docker-desktop dev: Docker Dev Environments (Docker Inc.) Version: v0.1.2 Path: /Users//.docker/cli-plugins/docker-dev extension: Manages Docker extensions (Docker Inc.) Version: v0.2.25 Path: /Users//.docker/cli-plugins/docker-extension feedback: Provide feedback, right in your terminal! (Docker Inc.) Version: v1.0.5 Path: /Users//.docker/cli-plugins/docker-feedback init: Creates Docker-related starter files for your project (Docker Inc.) Version: v1.3.0 Path: /Users//.docker/cli-plugins/docker-init sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.) Version: 0.6.0 Path: /Users//.docker/cli-plugins/docker-sbom scout: Docker Scout (Docker Inc.) Version: v1.13.0 Path: /Users//.docker/cli-plugins/docker-scout

Server: Containers: 64 Running: 34 Paused: 0 Stopped: 30 Images: 37 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: 2 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 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 cgroupns Kernel Version: 6.10.4-linuxkit Operating System: Docker Desktop OSType: linux Architecture: aarch64 CPUs: 9 Total Memory: 7.655GiB Name: docker-desktop ID: 61f1d177-fb24-4ce6-8aaa-98017186dd7f 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=unix:///Users//Library/Containers/com.docker.docker/Data/docker-cli.sock Experimental: false Insecure Registries: 192.168.50.30:3000 192.168.50.30:8082 hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false

Builders list

NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS ci-builder* docker-container
_ ci-builder0 _ desktop-linux running v0.16.0 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6 ci-builder-artifactory docker-container
_ ci-builder-artifactory0 _ desktop-linux inactive
ecstatictu docker-container
\
ecstatictu0 \ desktop-linux inactive
jovialvillani docker-container
\
jovialvillani0 \ desktop-linux inactive
lucidvillani docker-container
\
lucidvillani0 \ desktop-linux inactive
musingelion docker-container
\
musingelion0 \ desktop-linux inactive
objectivebartik docker-container
\
objectivebartik0 \ desktop-linux inactive
pedanticishizaka docker-container
\
pedanticishizaka0 \ desktop-linux inactive
pricelesspascal docker-container
\
pricelesspascal0 \ desktop-linux inactive
recursingshtern docker-container
\
recursingshtern0 \ desktop-linux inactive
romanticbhaskara docker-container
\
romanticbhaskara0 \ desktop-linux running v0.16.0 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6 sweetlichterman docker-container
\
sweetlichterman0 _ desktop-linux inactive
default docker
_ default _ default running v0.15.2 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6 desktop-linux docker
_ desktop-linux \
desktop-linux running v0.15.2 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6

Configuration

The Dockerfile isn't the issue since the build completes successfully, but the problem occurs when pushing to the repository—it doesn't work as expected.

Build logs

No response

Additional info

No response

toby-griffiths commented 2 weeks ago

I'm also seeing this issue. Only just started using his, so not sure if it's a longer standing issue.