Docker-host IP wrong in pinata list

Docker Desktop
1

Expected behavior

According to pinata list the docker-ipv4 is 192.168.65.2

Actual behavior

Docker host ip is 192.168.64.3

Information

:spouting_whale: hostname = docker
Hostname of the virtual machine endpoint, where container ports will be
exposed if using nat networking. Access it via ‘docker.local’.

:spouting_whale: hypervisor = native (memory=2, ncpu=4)
The Docker.app includes embedded hypervisors that run the virtual machines
that power the containers. This setting allows you to control which the
default one used for Linux is.

▸ native: a version of the xhyve hypervisor that uses the MacOSX
Hypervisor.framework to run container VMs. Parameters:
memory (VM memory in gigabytes), ncpu (vCPUs)

:spouting_whale: network = hostnet (docker-ipv4=192.168.65.2, host-ipv4=192.168.65.1)
Controls how local containers can access the external network via the
MacOS X host. This includes outbound traffic as well as publishing ports
for external access to the local containers.

▸ hostnet: a mode that helps if you are using a VPN that restricts
connectivity. Activating this mode will proxy container network
packets via the Docker.app process as host socket traffic.
Parameters: docker-ipv4 (docker node), host-ipv4 (host node)
▸ nat: a mode that uses the MacOS X vmnet.framework to route container
traffic to the host network via a NAT.

:spouting_whale: filesystem = osxfs
Controls the mode by which files from the MacOS X host and the container
filesystem are shared with each other.

▸ osxfs: a FUSE-based filesystem that bidirectionally forwards OSX
filesystem events into the container.

:spouting_whale: native/port-forwarding = true
Expose container ports on the Mac, rather than the VM

▸ true: Container ports will be exposed on the Mac
▸ false: Container ports will be exposed on the VM

:spouting_whale: daemon = run ‘pinata get daemon’ or 'pinata set daemon [@file|-]>
JSON configuration of the local Docker daemon. Configure any custom
options you need as documented in:
https://docs.docker.com/engine/reference/commandline/daemon/. Set it
directly, or a @file or - for stdin.

OSX 10.11.3
Docker Version 1.11.1-beta11 (build: 6974)

Steps to reproduce the behavior

  1. …
  2. …
2

Could you send the output that is leading you to believe that the IP address is different?
This only shows what the configuration database sees…

3

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
856b10a00426 innroad/swagger-ui “/bin/sh -c './node_m” 5 seconds ago Up 2 seconds 192.168.64.3:8080->8080/tcp swagger-1
936cc51fc989 mongo “/entrypoint.sh mongo” 5 seconds ago Up 2 seconds 192.168.64.3:27017->27017/tcp mongo-1
6c66c49a777e postgres “/docker-entrypoint.s” 5 seconds ago Up 2 seconds 192.168.64.3:5432->5432/tcp postgres-1
0e4b38e1f58b devopsdockerlocaldev_dynamodb "/bin/sh -c 'java " 5 seconds ago Up 2 seconds 192.168.64.3:8000->8000/tcp dynamodb-1
f0d086c02542 rabbitmq:3-management “/docker-entrypoint.s” 5 seconds ago Up 2 seconds 4369/tcp, 5671/tcp, 192.168.64.3:5672->5672/tcp, 15671/tcp, 25672/tcp, 192.168.64.3:15672->15672/tcp rabbit-1