#Hey guys, I just missed last release
1 messages ยท Page 1 of 1 (latest)
it seems related but not exactly same.
Currently I'm having trouble to find way,
- Loading working automatically like we do with
Hostand loading unix sockets fromHost
I know we removed Host in https://github.com/dagger/dagger/pull/6535
not 100% sure what the plan for UnixSocket is though
So I think the idea would be to explicitly pass unix sockets around as well
But I don't think it's possible to create them at the CLI today sadly
it would be really nice if we could pass a unix socket through a flag: we'd need it in here https://github.com/dagger/dagger/blob/main/cmd/dagger/flags.go#L340-L344
@narrow sequoia what are you using the unix socket for? What's its path? Need some real user data to decide on a design ๐๐
sometime I need to access docker using cli and I'm forwarding custom docker unix socket to gale container using host and optional user input
This is just an example code to use native docker
// configure docker using docker host when docker is enabled and dind is not enabled
if r.RunnerOpts.UseNativeDocker && !r.RunnerOpts.UseDind {
switch {
case strings.HasPrefix(r.RunnerOpts.DockerHost, "unix://"):
dh := strings.TrimPrefix(r.RunnerOpts.DockerHost, "unix://")
ctr = ctr.WithUnixSocket("/var/run/docker.sock", dag.Host().UnixSocket(dh))
ctr = ctr.WithEnvVariable("DOCKER_HOST", "unix:///var/run/docker.sock")
case strings.HasPrefix(r.RunnerOpts.DockerHost, "tcp://"):
ctr = ctr.WithEnvVariable("DOCKER_HOST", r.RunnerOpts.DockerHost)
default:
return nil, fmt.Errorf("unsupported docker host: %s", r.RunnerOpts.DockerHost)
}
}
it's okay to ditch unix socket and Host().Directory but I would need to similar solutions to workaround these issues
We have a talk tomorrow in Berlin Devops Meetup and trying to update some project codes, that's why it's kind a urgent :/
aha, nice timing ๐ we're doing v0.9.9 tomorrow, though not sure if we'll get any unixsocket support in before then (depends on busy-ness levels)
no worries, I'm already rolled back 0.9.5. If there is no workaround, i'll use this version
no need to keep latest in the talk
Ah, you need to access a unix socket in your local machine's filesystem
So it's this problem: #daggernauts message
So the solution is not a missing host function, but supporting socket arguments in the CLI @tidal echo @wicked cypress
yea seems like it. I don't have any preference about the way. I said host since it was containing functionality but I'm okay with any type of access.
supporting socket arguments feels better. ๐โโ๏ธ