sciabarracom commented on a change in pull request #3182: Fixes to Vagrantfile
URL:
https://github.com/apache/incubator-openwhisk/pull/3182#discussion_r161296484
##########
File path: tools/vagrant/Vagrantfile
##########
@@ -159,7 +159,7 @@ $script_end = <<SCRIPT
touch $HOME/.wskprops
chown -R vagrant:vagrant $HOME
# This allows user to see how to configure the wsk cli outside the VM
- wsk property set --apihost ${WHISK_IP} --namespace guest --auth `cat
${ANSIBLE_HOME}/files/auth.guest`
+ wsk property set --apihost http://${WHISK_IP}:10001 --namespace guest --auth
`cat ${ANSIBLE_HOME}/files/auth.guest`
Review comment:
First note the error is (inside the vm, AFTER a vagrant halt / vagrant up -
I know docs says to use susped) :
$ wsk action list
error: Unable to obtain the list of actions for namespace 'guest': Get
https://192.168.33.13/api/v1/namespaces/guest/actions?limit=30&skip=0: dial tcp
192.168.33.13:443: getsockopt: connection refused
Then:
$ docker ps | grep nginx
aeb333ed2b95 nginx:1.11 "nginx -g 'daemon off" 5
hours ago Restarting (1) About an hour ago 0.0.0.0:80->80/tcp,
0.0.0.0:443->443/tcp, 0.0.0.0:8443->8443/tcp nginx
$ curl -k https://0.0.0.0:443/api/v1
curl: (35) Unknown SSL protocol error in connection to 0.0.0.0:443
$ curl -k https://localhost:443/api/v1
curl: (35) Unknown SSL protocol error in connection to localhost:443
$ curl -k https://172.17.0.1:443/api/v1
curl: (7) Failed to connect to 172.17.0.1 port 443: Connection refused
I am pretty sure the reason of this is the halt/up but I was trying to
understand why a restart of a vm is so destructive.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
