-
Notifications
You must be signed in to change notification settings - Fork 466
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
add "env" driver that connects to $BUILDKIT_HOST #23
Comments
Otoh, combining may add complexity as #21 is linux only and may require credentials while this could work from anywhere. It would be easier to do this split by using different drivers. |
+1 This would be awesome! |
Any updates regarding this issue? Is it there another way to run buildx with a remote buildkitd? |
Hello folks, kindly ping 🙋🏻♂️✌️ Are there any updates? We (w/@Dentrax) thought that, if it happens, we can be able to use the buildkitd running in lima-vm for this. So, we are so excited about this. |
Nobody is working on it afaik. It should quite easy to add it If somebody wants to take it on. Most of the work would probably be to make sure that CI would test this driver. |
@jedevc thanks for the feature, what do you think about: docker/for-mac#6149 ? |
Hi @tonistiigi @jedevc , |
The buildx-bin image has the You're right, the remote driver is still not in a release of buildx yet, but it will be in the next release of buildx with v0.9. We've got a milestone of issues/prs that are targeted towards that release as well: https://github.com/docker/buildx/milestones/v0.9.0 - it's in progress. |
This driver allows creating a buildx instance directly pointing to the existing buildkit endpoint.
docker buildx create --driver=env unix:///var/lib/buildkitd.sock
docker buildx create --driver=env
usesBUILDKIT_HOST
env value with UNIX sock default.I guess TLS info is just passed with a custom driver-opt:
rm/stop
commands are no-op in this driver.A better name could be "remote".
The text was updated successfully, but these errors were encountered: