Expected behavior There will be docker0 interface/bridge available with an IP address to which I can bind services running on the host. This address will not be accessible from outside my Mac. Actual behavior Starting with beta9, there is no such interface - to see host-based services from within …

Actually, I’ve worked this around by duplicating an existing interface and manually assigning it an IP address of my choice.

@mnowrot Can you provide some details on yow you worked around this? Lacking bridge100, I have to idea how to connect to a service running in the container, such as sshd on port 22.

@ctaggart starting with beta9, the sshd service running in a container should be available on localhost:22 on the host. You can connect to it as you would to any service running on localhost (assuming that this service has bound to proper interfaces inside the container, and that default configurati…

@mnowrot That explanation really helped! I now have it working.

You can get bridge100 back. $ pinata set network nat $ ifconfig You should see bridge100 as a network interface again.

Bridge100 bridge unavailable on host

Docker Desktop

mnowrot (Marcin Nowrot) May 12, 2016, 2:34pm 6

There was a more elegant solution proposed: Access host (not vm) from inside container

Topic		Replies	Views
Host excluded from bridge network Docker Desktop	11	7911	July 6, 2016
Network bridge on host Docker Desktop beta , macos	6	24452	October 17, 2023
I don't see host ip 192.168.x.x. In ifconfig Docker Desktop	7	3431	April 29, 2016
Docker beta network not accessible form host machine Docker Desktop beta	1	2497	June 29, 2016
Cannot access network port on host using bridge network Docker Desktop	1	14281	August 5, 2016

Bridge100 bridge unavailable on host

Related topics