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
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.
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)
docker buildx use remote
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"
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 theremote
package hereI 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:
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)docker buildx use remote
docker compose
with buildkit/buildxDescribe the results you received:
Describe the results you expected:
It builds!
Output of
docker compose version
:Output of
docker info
:Additional environment details:
The text was updated successfully, but these errors were encountered: