You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/03/19 17:31:06 UTC

[GitHub] develpr commented on issue #3465: Provisioning new VM with vagrant fails because there is no `vagrant` user

develpr commented on issue #3465: Provisioning new VM with vagrant fails because there is no `vagrant` user
URL: https://github.com/apache/incubator-openwhisk/issues/3465#issuecomment-374298412
 
 
   Confirmed! That was indeed the issue. I for some reason thought that Vagrant would automatically force an upgrade of the base box, or that the base box version constraint was somehow part of the `Vagrantfile`.
   
   For anybody who finds this in the future, 
   
   `vagrant box remove ubuntu/xenial64`
   
   and then `vagrant up` (or `./hello`) seems to have resolved this issue for me.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services