-
Notifications
You must be signed in to change notification settings - Fork 162
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] Missing bosh create-env support #626
Comments
@ZPascal Could you try removing those lines and check if the VirtualBox CPI gets any further? There is no point in removing those lines if the VirtualBox CPI does not work, given that there are no other CPI's that want to support windows. |
@rkoster Do you mean the corresponding lines inside the bosh CLI? I'll organize a Windows machine and try it out. |
Yes the corresponding lines inside the bosh cli. |
@rkoster I've removed the code lines and tested it again on the Windows machine. Now, I've faced another issue, but not directly related anymore to the Bosh CLI. Do you have ever seen that issue or should I start to debug it? |
@ZPascal can this issue be closed? |
@rkoster No, I have not fixed the issue/ tested the solution yet. As a follow-up, I'll definitely open a PR inside this repository to adjust the used version of the utils implementation. |
FYI @rkoster & @beyhan To give you an update on that topic. I've executed the I'll further work as a side topic on it, but how should we continue with this topic? Should I open the corresponding PR to adapt the Bosh CLI or should we roll it out, if everything works as expected (my preferred solution)? |
The |
Hi @bgandon, for me it looks like BOSH wants to compile the Golang CPI part with classical Bash syntax. Do you have any idea, where I can find the corresponding part inside the source code?
|
The compilation is happening down here |
@jpalermo Thank you for pointing me to the right code lines. I'll check the possible options. |
Hi community,
we've faced the case that currently the
create-env
parameter is not supported by the bosh cli.How we've identified the case?
We've faced the case thats it's not possible to use the Bosh Lite on Windows machines.
Background information:
Bosh Lite setup
The text was updated successfully, but these errors were encountered: