-
Notifications
You must be signed in to change notification settings - Fork 192
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
Cannot create environment in vagrant #1
Comments
Hello, I don't know if it is the same issue but in my case the error trace
Which is related to an untrusted SSL key. To fix it, i just i've added the public ssh key to my
Once done, modify the
And that's all, you are ready to execute Note: you must do same steps for every host which is not working. HTH |
Is this still an issue? |
I am a bit busy now and I didn't tried after my last answer. Maybe @konradstarzyk could give you some feedback. |
I'm hoping to try out SaltStack and just encountered a similar issue when following the Getting Started Guide. It doesn't seem to be on
Error I see when doing
|
I've managed to make a little progress by incorporating the PR: #8 I now get the following error:
I could create a separate issue if desired/necessary but this seems a good place to discuss general Vagrant issues. This demo should work out of the box as it is the recommended (easy) way to learn Salt. |
Had some time to look at this some more. My last issue seems to be a known issue: hashicorp/vagrant#5973 I'm now giving on this Vagrant setup as I'm spending way too much time troubleshooting Vagrant rather than learning Salt itself - I'll probably try a manual install instead. |
Hello, |
I replaced
with
in the VagrantFile. That solved the issue for me. |
This has been fixed. |
I get this on Ubuntu 16.10 (not inside a Vagrant VM) and this is the only link that shows up when I google for help. Does anyone know what the root cause for this issue is? |
Move to salt-formulas organization.
I cloned the repository and did "vagrant up". I am getting the following error:
Processing triggers for python-support ...
allow cloning disabled
fatal: The remote end hung up unexpectedly
Cloning into 'salt'...
Stderr from the command:
stdin: is not a tty
The text was updated successfully, but these errors were encountered: