Hi Sorcerer Stone,

So the netstat output and the `docker container ls` helps us understand 
what is happening. So I'll repeat the details here.

a567856275d4        ohif/viewer:v1.x                 "pm2-runtime app.json"   2 
days ago          Up About a minute   3000/tcp                                  
    ohif
948af342718c        jodogne/orthanc-plugins:latest   "Orthanc /etc/orthan…"   2 
days ago          Up About a minute   4242/tcp, 8042/tcp                        
    orthanc
003ba380169e        postgres:latest                  "docker-entrypoint.s…"   2 
days ago          Up About a minute   5432/tcp                                  
    db_orthanc
701123a4caa7        mongo:latest                     "docker-entrypoint.s…"   2 
days ago          Up About a minute   27017/tcp                                 
    db_ohif
f00c419b32ba        nginx:latest                     "nginx -g 'daemon of…"   2 
days ago          Up About a minute   0.0.0.0:9080->80/tcp, 
0.0.0.0:9443->443/tcp   nginx


You have 5 docker containers. And only nginx is doing port-forwarding. 
nginx is in fact a reverse proxy, meaning that most likely you're accessing 
nginx in order to contact all the other containers. Therefore, if you can 
access 9443 and 9080 from the VM then you're good (from the perspective of 
the VM).

So you'll notice that the docker container with image name 
jodogne/orthanc-plugins:latest is listening on port 4242 (but it's not 
forwarding port 4242!). I believe you're calling this container "AppDock" 
(and AppWin is running on the host). As you can see by the container, it is 
not forwarding the port. You should check the nginx container and see if it 
is proxying communication to AppDock. So basically, the host "AppWin" 
cannot reach docker container "AppDock" because how is it supposed to reach 
it?

Basically, AppDock needs to do port-forwarding (so that the VM can reach 
the container) or AppWin should try to go through the reverse proxy, nginx, 
to reach the docker container service listening on port 4242.


-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/de44d4e0-1501-40a7-b986-42291bde375f%40googlegroups.com.

Reply via email to