search

riebl / artery

OMNeT++ V2X simulation framework for ETSI ITS-G5
GNU General Public License v2.0
203 stars 129 forks source link

Problems with vagrant on Windows #267

Closed Mondraupe closed 1 year ago

Mondraupe commented 1 year ago

Hi, I would like to use Artery on a VM on windows. I can run "vagrant up" from Artery's root directory, but the login credentials that are written on the website don't work (username: "vagrant", pw: "vagrant"). I can login with username: "root" and pw: "vagrant", but with this login I haven't any directorys. Could you tell me what i did wrong?

riebl commented 1 year ago

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?

riebl commented 1 year ago

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

Mondraupe commented 1 year ago

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.

riebl commented 1 year ago

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.