Problems with vagrant on Windows about artery HOT 4 CLOSED

Hi @Mondraupe,

I don't think that you have done anything wrong. My guess is that the default setup of Vagrant (or at least the used Debian box) has changed, in particular, the "vagrant" user login has been disabled.
As a workaround, just can explicitly set the password for "vagrant" when logged in as "root": passwd vagrant
I suppose the problem is only with the lock screen, right?

from artery.

I have updated the Vagrant setup with 9764979. You may want to give it a try.

from artery.

Thanks for the reply. I tested the new Vagrant setup and set the password for vagrant with passwd vagrant.
Now i can login as vagrant, but there are no input files. So i can't go to /artery-build/ and start artery as described on the website.

from artery.

Sounds like something went wrong during the initial provisioning of the machine by Vagrant. You may either destroy the VM and start from scratch again with a fresh machine or explicitly run the provisioning steps again with vagrant up --provision.

from artery.