Devops, personal windows machine setup
- or -
Post a project like this$$$
- Posted:
- Proposals: 0
- On-site in Wroughton, GB
- #1887855
- Expired
Description
Experience Level: Expert
Estimated project duration: 1 day or less
We need a developer machine configured to work with vagrant + VirtualBox. Ideally someone could come in for an afternoon to help get this setup to our office just outside Swindon.
We have hit an issue that looks similar to what is in the following thread:
https://github.com/hashicorp/vagrant/issues/8157
We have tried some of the things from this thread with no luck to progressing any further.
We have used ssh successfully from this machine before, we have git installed and SSH is in the PATH for this machine. Also we have tried using putty to connect to the details given by ‘vagrant ssh-config’ with no luck (gives an error: Connection refused).
Computer has windows 10 home with virtualisation tech enabled through the bios. We are trying to use vagrant with the https://app.vagrantup.com/bento/boxes/centos-6.8 box set up using virtualbox. Everything is fine up until the ‘vagrant up’ command where vagrant hangs (doesn’t provide an error message) at the ‘SSH auth method: private key’.
We have tried setting this up on another machine (an apple machine) and can confirm that this image works.
We have hit an issue that looks similar to what is in the following thread:
https://github.com/hashicorp/vagrant/issues/8157
We have tried some of the things from this thread with no luck to progressing any further.
We have used ssh successfully from this machine before, we have git installed and SSH is in the PATH for this machine. Also we have tried using putty to connect to the details given by ‘vagrant ssh-config’ with no luck (gives an error: Connection refused).
Computer has windows 10 home with virtualisation tech enabled through the bios. We are trying to use vagrant with the https://app.vagrantup.com/bento/boxes/centos-6.8 box set up using virtualbox. Everything is fine up until the ‘vagrant up’ command where vagrant hangs (doesn’t provide an error message) at the ‘SSH auth method: private key’.
We have tried setting this up on another machine (an apple machine) and can confirm that this image works.
Kevin S.
100% (20)Projects Completed
22
Freelancers worked with
20
Projects awarded
58%
Last project
18 May 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies