-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP_PROXY and HTTPS_PROXY are not automatically forwarded to the Vagrant VM #23
Comments
I had this same issue and was able to work around it by editing the vagrant/bootstrap.sh script. First, I copied my resolved http_proxy and https_proxy variables into the top of the script. Then I added Run |
This is likely a connectivity issue, and based on your proxy environment variables being set, the solution should be to forward that to Vagrant: Run Change your
Then do You can ssh into the machine using Edit: Setting the proxy variables in bootstrap.sh as per zbobbert's reply should work as well. |
I will add a note to the quorum-examples README about this. Thanks guys. |
Thanks a lot. it worked ! notes in readme will surely help |
Couple of more changes needed for making the example work if you are on Windows (I am on 8.1) In order to login into VM through putty, the private_key file needs to be converted using puttygen and then only putty accepts the key file to login. I loaded the /quorum-examples/.vagrant/machines/default/virtualbox/private_key into puttygen
After that... the steps mentioned work (./init.sh, followed by ./start.sh) |
System information
Geth version: 1.3.5
OS & Version: Windows 8.1
Commit hash : (if
develop
)On firing Vagrant up, I am facing the following issue
==> default: Running provisioner: shell...
default: Running: C:/Users/00000/AppData/Local/Temp/vagrant-shell20161130-4056-1lsawh4.sh
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: Cannot add PPA: 'ppa:~ethereum/ubuntu/ethereum'.
==> default: ERROR: '~ethereum' user or team does not exist.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Are there steps I am missing ? also what's the password used for ubuntu user for this virtual box image ? if that's available, I can try logging into the machine separately and check issue with ppa. I have http_proxy and https_proxy set.
The text was updated successfully, but these errors were encountered: