https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Can you file one on Rancher Desktop too, even if just a link to the Act one?
q
Maybe tonight
f
Sorry, can't concentrate on this. The important part is that you can only bind socket paths from the guest into the container. Mounting a filesystem does not forward unix sockets.
q
so you think something's getting confused and using 
mount
instead of 
bind
?
f
Since /var/run/docker.sock exist inside the guest, you can just forward it directly, even if it doesn't exist under this path on the host
No I think something is bind-mounting
Copy code
/Users/steven/.docker/run/docker.sock
into the container as /var/run/docker.sock, and that will not work.
You need 
-v /var/run/docker.sock:/var/run/docker.sock
q
err, ok, so it's using 
bind
instead of 
mount
? 🙂
f
docker run ... -v
is using bind mounts.
Sorry, I have no time to look into this right now; this is the only hint I can give you: containers cannot access host sockets, they can only bind-mount guest sockets.
For 
docker.sock
that is just as well, as the host socket is just a guest socket forwarded over ssh. You wouldn't go through 2 forwarding tunnels back and forth if you could just connect locally
But there is nothing to. tunnel it back to the guest anyways, so connecting to the host socket will just fail
q
if you can look at it later, that's also fine. i can try to proxy concepts over or make small tweaks to act, but all of the layers of nesting make me dizzy
f
I have a bunch of several audacious goals this week, so won't look at anything else, sorry
q
doesn't have to be this week 🙂
good luck w/ your goals
f
Thanks!
7 Views
Open in Slack
PreviousNext
Powered by