Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failed to find buildx driver "remote" #9893

Closed
benmoss opened this issue Oct 4, 2022 · 3 comments · Fixed by #10226
Closed

failed to find buildx driver "remote" #9893

benmoss opened this issue Oct 4, 2022 · 3 comments · Fixed by #10226

Comments

@benmoss
Copy link
Contributor

benmoss commented Oct 4, 2022

Description
Buildx introduced a remote driver, where you can just connect to an existing buildkit daemon.

Looks like we can just bump buildx and add a _ import to the remote package here

I tried doing this myself but ran into some issues since buildx needs some unreleased feature from buildkit, and docker/cli and docker/docker both needed to get bumped too, and then there were compilation problems 😥 . Left a branch pushed with a WIP here.

Steps to reproduce the issue:

  1. Create a buildkit server (I followed this guide)
  2. Wire it up to docker-buildx (docker buildx create --name remote --driver=remote --driver-opt key=$PWD.certs/client/key.pem --driver-opt cert=$PWD/.certs/client/cert.pem --driver-opt cacert=$PWD/.certs/client/ca.pem tcp://127.0.0.1:1234 if you're following that guide)
  3. docker buildx use remote
  4. Try to use docker compose with buildkit/buildx

Describe the results you received:

$ docker-compose run app py.test
failed to find buildx driver "remote"

Describe the results you expected:
It builds!

Output of docker compose version:

Docker Compose version 2.11.2

Output of docker info:

Client:
 Context:    colima
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.9.1)
  compose: Docker Compose (Docker Inc., 2.11.2)

Server:
 Containers: 15
  Running: 3
  Paused: 0
  Stopped: 12
 Images: 18
 Server Version: 20.10.18
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  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 logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc version: 5fd4c4d144137e991c4acebb2146ab1483a97925
 init version:
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.15.68-0-virt
 Operating System: Alpine Linux v3.16
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 3.828GiB
 Name: colima
 ID: L6MV:2NHB:DMC5:7ABF:UAJK:HDHG:WXSX:GSK4:D2MH:NXMP:XATY:KXOH
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Username: benmoss
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  host.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details:

$ docker buildx version
github.com/docker/buildx v0.9.1 ed00243a0ce2a0aee75311b06e32d33b44729689
@enys
Copy link

enys commented Feb 1, 2023

I seem to be facing the same issue. Did you find a way to get it to work ? I have Docker Compose version v2.15.1

@benmoss
Copy link
Contributor Author

benmoss commented Feb 1, 2023

Nope, no workarounds afaik, there needs to be code changes in compose to get this to work

@benmoss
Copy link
Contributor Author

benmoss commented Feb 1, 2023

@enys thanks for pinging me though, it looks like the various dependency problems have been fixed and this is a really simple fix now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants