Hello Dennis, Thanks for the tips. Based on what you told me, I found something disturbing. I have googled for solution but maybe I am not keying in the right words, I found nothing to solve this problem (below).
I attached 2 files for your inspection. My vagrantfile (same as the one I sent yesterday) and the output of the netstat command (netstat_missingports.txt). I have attached the ifconfig in my previous post if you want to look at it. First the vagrantfile: line 37: I have port forwarded port 443 from guest to port 9443 at host line 38: I have port forwarded port 80 from guest to port 9080 at host line 39: I have port forwarded port 4242 from guest to port 4241 at host As confirmation, I reattached the screenshot of the network setting in the VirtualBox VM for AppDock. The image, NAT & PortForwarding.jpg, shows VM does "see" all the 3 forwarded ports. Now, when I did the netstat command as you advised (refer to the attached file netstat_missingports.txt), port 4242 is glaringly missing! No wonder nothing is going from the host side to the VM. Would you have any suggestion as to how I need to modify the vagrantfile in order for port 4242 to be forwarded? Also, I am not clear what you said about "when you do port-forwarding between docker (i.e. docker-compose) and the VM you are making a docker service available to the VM (but not to the host!!)." Can you elaborate a bit more? Isn't the port forwarding statements in my vagrantfile is telling the VM routing the relevant ports between the host and the guest? I can access the AppDock using its UI via port 9443. So that port is working. Also, as I mentioned before, from the UI of the AppDock VM, I can send data to the AppWin using the port # of AppWin and the IP address of my host computer (aka not the private network IP address stated in my vagrantfile) & the AppWin received this data. How can this happen? Thanks in advance. Sorcerer -- 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/c972f289-7a11-4d98-9c56-29a882f1484e%40googlegroups.com.
vagrant@vagrant:~$ docker network ls
NETWORK ID NAME DRIVER SCOPE
f178c2bfeb7b bridge bridge local
d71aa7885ba1 host host local
1e7a33e6e027 none null local
f9fea8d91504 vagrant_default bridge local
vagrant@vagrant:~$ docker container ls
CONTAINER ID IMAGE COMMAND
CREATED STATUS PORTS
NAMES
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
vagrant@vagrant:~$ netstat -tlpn
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
-
tcp6 0 0 :::22 :::* LISTEN
-
tcp6 0 0 :::9080 :::* LISTEN
-
tcp6 0 0 :::9443 :::* LISTEN
-
tcp6 0 0 :::111 :::* LISTEN
-
vagrantfile
Description: Binary data
