#Hey folks so I ve been using a remote
1 messages · Page 1 of 1 (latest)
I was hoping the docker-container method might still work but looks like buildkit host expects a tcp protocol and there's docker-container:// here .https://github.com/dagger/dagger/blob/main/internal/engine/docker.go#L91
@wicked sable that's correct. There's been some changes in the architecture lately that removed that capability. I'll defer this to @timber lantern or @normal vessel since they have more context about why that was changed.
I know Solomon had a verison matrix concern and wanted to pack buildkit with dagger engine but I sorta liked the "do it at your own peril" way which worked at the time.
Actually, if I can connect to dagger engine remotely, that would be great too.
well.. you can. cloak dev listens in a TCP port, so that shouldn't be a problem
I think I tried that in the past. Issue was that I can't connect to the Dagger engine via tcp/http. It seems to only support unix / embedded , I don't know if support for tcp/http is added?
cloak dev currently supports it https://github.com/dagger/dagger/blob/main/cmd/cloak/dev.go#L29-L35
that starts a tcp server in the specified port
Awesome! I'll try it out, thanks 🙂
Hi, it's been replaced by DAGGER_HOST
@pseudo imp it's not the same thing. DAGGER_HOST is the host to our helper binary, not buildkitd
I also found about it yesterday 😄 things move fast here :sonic:
Yeah, I was previously running buildkit on a remote host but dagger engine locally
Btw, my TestImageProvision keeps failing locally, I don't know why
I don't know how the file related operations will work anymore. Only one way to find out
if you connect remotely to cloak dev host file system access will not work. That’s why we’ve temporarily disabled the feature. Don’t connect remotely to cloak dev it won’t work the way you hope
we’re in a complicated in-between right now, but there’s a PR underway to fix it
Yeah.. Solomon's right, I misinterpreted your "file operations" comment with something else