-
Notifications
You must be signed in to change notification settings - Fork 160
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
[windows] bosh add-blobs failed #278
Comments
I have a similar problem when running "bosh create-env" on Windows:
Seems to be a problem in the |
I wonder if we're forgetting to close the original file before attempting to move - Windows seems particularly picky about that. |
@Fydon
Did you hit the above error before? |
@bingosummer That error is because the folder containing |
Thanks @Fydon . The BSD tar works for me. I put the BSD tar in my PATH environment. Is it the correct way? But I got another error about The detail error message:
|
@bingosummer Yes I started looking into that problem, but then thought I'd try get bosh-virtualbox-cpi-release working on Windows, as I'm currently using bosh-lite via vagrant, which I understand is no longer maintained. I plan to get back to looking into this soon and will update this if I get further. |
same issue on windows with
Any workaround or fix? |
@sumkincpp The last release was created 14 days ago, so you either need to built it yourself or wait for the version after 2.0.33 for |
There is a tonights artifact for 2.0.34 bosh-cli-2.0.34-windows-amd64.exe, I'll give a try and report back. |
So there is an issue with tar after that, tar.exe is present in $PATH
|
@sumkincpp Thank you for letting me know about the new build. I think you need to apply my pull request in a custom build of bosh-cli to get that tar to work, otherwise use BSD tar.
|
@sumkincpp I'm still working on it, but this patch should get you through the compile phase, which is basically using Powershell instead of bash, dropping |
Sorry my last suggestion was foolish, however now I have managed to get compiling working. I don't know if it will work for all CPIs, but I can get Currently my branch is using the MSYS bash that comes with git for Windows, as I was having problems when using Windows Subsystems for Linux. |
@Fydon. and still can't get passed the UseIsolatedEnv issue. But you said there are still issues on the last branch you have ? |
@saedalav Sorry I've been busy recently so not had much spare time to work on this. I've now reopened the above pull request with the changes that are required to help compiling work. Compiling and running the CPI may require Linux or even Ubuntu specific commands, but I am able to compile |
Hi, Any update on when Bosh Lite installation is supported on windows? C:\BOSH\deployments\vbox>bosh create-env ../../workspace/bosh-deployment/bosh.yml --state ./state.json -o ../../workspace/bosh-deployment/virtualbox/cpi.yml -o ../../workspace/bosh-deployment/virtualbox/outbound-network.yml -o ../../workspace/bosh-deployment/bosh-lite.yml -o ../../workspace/bosh-deployment/bosh-lite-runc.yml -o ../../workspace/bosh-deployment/jumpbox-user.yml --vars-store ./creds. Started validating ←[31mExtracting release '.bosh\downloads\00408810832ec663212900fc4810385a230d4dbf-f262d1c35f3646a3f0394132f2705719c9d2bb6a': ←[31mExit code 1←[0m |
my current environment Extracting release 'C:\Users\king.bosh\downloads\62d4fa7ad92f03d289c8a25c69631c683e1052f3-3850c68124bf5bce3cfb1433cce52e2d67741d94': gzip: stdin: unexpected end of file Exit code 1 Please let me know any solutions for this |
It seems like this issue is diverging into another conversation about create-env. Since the original If you want to continue to discuss the create-env concerns, please open a new issue with later versions of the bosh-cli. |
The text was updated successfully, but these errors were encountered: