-
Notifications
You must be signed in to change notification settings - Fork 557
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
Vagrant Box Add fails on windows #110
Comments
I'm hoping we can move everyone to the Perhaps you can try installing Then try deploying Concourse to Virtualbox using:
If this works, please follow along with the upgraded tutorials at https://concoursetutorial.com/ (will make this more public soon once I've finished upgrading tutorial instructions) and let me know. If you have issues, then please report them and we'll get them fixed for you! |
Hi,
|
I'm sorry I've moved away from the vagrant up instructions that worked for
windows. I was hoping the `bosh create-env` instructions would work for
Windows but didn't get out my Windows laptop to check. I might continue
pursuing the bosh approach for Windows to drive fixes to bosh-cli + bucc
(which also is not for windows). If I fail, I'll return to the vagrant up;
but I don't have a solution to adding credhub/credentials via vagrant so I
worry we lose the Windows people later on. But I guess that's better than
losing them at the start :)
|
I found the best way to get started was using docker using the instructions here: https://concourse.ci/docker-repository.html |
@choumarin do you remember what adaptation of the instructions were required? I'm happy to put something into the tutorial to help Windows people. |
@drnic you might find this useful |
Since https://github.com/starkandwayne/concourse-tutorial/releases/tag/v3.10.0 we're moving towards |
I've gotten the same problem with Vagrant v. 1.9 and 2.0.1 - running the command
vagrant box add concourse/lite --box-version $(cat VERSION)
gives me this message & error:
so I can't get the vagrant box even running.
The text was updated successfully, but these errors were encountered: