windows - Can't Configure Remote Access of Docker Host -
i did successful docker windows install on 2 windows machines (windows 10 , windows 7 x64 sp1). can perform administration duties of docker hosts through terminal services (rdp) or through powershell remoting.
however, docker documentation indicates docker host offers own restful remote api administration. use api. problem in examples given in documentation, client invocations (via curl
) physically on same box docker host. in other words not remote and, unfortunately, steps adapt remote scenario not obvious.
for example, consider command taken straight documentation:
curl --insecure --cert ~/.docker/cert.pem --key ~/.docker/key.pem https://your_vm_ip:2376/images/json
obviously need your_vm_ip
proceed. on both of windows boxes type docker-machine ls
. discover on both physical windows machines address docker host tcp://192.168.99.100:2376
.
oops. can't both have same ip address. virtualbox nat address local vm in both cases.
this primary issue. i'd know how expose externally visible docker host ip address can perform remote adminstration.
possibly issue less docker , more virtualbox. there several network interfaces , networking modes docker host vm configured (e.g. nat, bridge, internal, host only. perhaps combination allow ip of docking host vm exposed.
or not? possibility i'm misunderstanding docker means "remote api". perhaps "remote" means don't need directly ssh docker host, from host machine, in order perform administration. however, don't think i'm misunderstanding - particularly when see quotes this:
by default, daemon can accept local connections on unix domain socket. taken from: docker machine basics
yes, have discovered "by default" indeed local. need know how make non-local, can provide remote administration. i've found no documentation anywhere.
any ideas?
i've found no documentation anywhere.
well, it's because "docker on windows" hack intended local development on single box.
everyone running docker in production (i.e. people need multiple boxes) run docker directly on linux no vms. orchestration technologies (kubernetes, etc) assume docker server has routeable ip address.
possibly issue less docker , more virtualbox.
correct. can "fix" problem exposing vm's port 2376 network. may have allow port in windows firewall too.
Comments
Post a Comment