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
Using #2843, I am able to talk to buildkitd through buildctl via SSH:
BUILDKIT_HOST=ssh://toaster ./buildctl build --frontend=gateway.v0 --opt source=docker/dockerfile --opt context=https://github.com/FuzzyMonkeyCo/monkey.git --opt build-arg:PREBUILT=1 --output=type=local,dest=$PWD/
# goes through with the build
However the equivalent docker command fails:
DOCKER_HOST=ssh://toaster DOCKER_BUILDKIT=1 docker build -o=. --platform=local --build-arg PREBUILT=1 https://github.com/FuzzyMonkeyCo/monkey.git
[+] Building 0.0s (0/0)
error: no valid drivers found: Get "http://docker.example.com/v1.24/info": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x00\x00\x06\x04\x00\x00\x00\x00\x00\x00\x05\x00\x00@\x00".
* Are you trying to connect to a TLS-enabled daemon without TLS?
As noted in #2839 I (uninstalled docker-ce and) only have /usr/local/bin/docker:
Docker and buildkitd have different APIs. You can't just point docker client to buildkit server. DOCKER_HOST != BUILDKIT_HOST.
What you want in here likely is to extend the docker buildx remote driver to also understand the ssh protocol. Currently it supports tcp and unixdocker/buildx#1086 .
Using #2843, I am able to talk to
buildkitd
throughbuildctl
via SSH:However the equivalent
docker
command fails:As noted in #2839 I (uninstalled docker-ce and) only have
/usr/local/bin/docker
:Note: I am running latest rootless
buildkitd
withPATH="$PATH:$HOME/bin" ~/bin/rootlesskit --net=slirp4netns --slirp4netns-sandbox=true --slirp4netns-seccomp=true --copy-up=/etc --disable-host-loopback ~/bin/buildkitd
Is it normal that (rootless)
buildkitd
is not usable directly viadocker
CLI?The text was updated successfully, but these errors were encountered: