create-env fails on Windows 10

[bendalby82]

I am trying to spin up BOSH Lite v2 usng VirtualBox, but my create-env command is failing on Windows 10 Enteprise (v1607, Os Build 14393.970).

I am using bosh-cli-2.0.42-windows-amd64, and have tried the command in both Powershell 5.1.14393.953 and the version of Git Bash that came with Git for Windows v2.14.2(3).

Here is the Powershell output

PS C:\Users\dalbyb1\GitHub\bosh-deployment> bosh create-env bosh.yml --state .\state.json -o virtualbox\cpi.yml -o virtu
albox\outbound-network.yml -o bosh-lite.yml -o bosh-lite-runc.yml -o jumpbox-user.yml --vars-store .\creds.yml -v direct
or_name="Bosh Lite Director" -v internal_ip=192.168.50.6 -v internal_gw=192.168.50.1 -v internal_cidr=192.168.50.0/24 -v
 outbound_network_name=NatNetwork
Deployment manifest: 'C:\Users\dalbyb1\GitHub\bosh-deployment\bosh.yml'
Deployment state: '.\state.json'

Started validating
  Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh'... Failed (00:00:00)
Failed validating (00:00:00)

Extracting release '.bosh\downloads\a9cb72bf8fa9b8b4a7e80e1ef2bd61f4c008cf1d-37630c636a030454d55703cfdd495d733525353f':
  Extracting release:
    Shelling out to tar:
      Running command: 'powershell tar --no-same-owner -xzf .bosh\downloads\a9cb72bf8fa9b8b4a7e80e1ef2bd61f4c008cf1d-376
30c636a030454d55703cfdd495d733525353f -C .bosh\installations\8861b2b8-be0a-4fbd-7b2a-9ef4b86e0a20\tmp\bosh-release784654
283', stdout: '', stderr: 'tar : The term 'tar' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ tar --no-same-owner -xzf .bosh\downloads\a9cb72bf8fa9b8b4a7e80e1ef2bd ...
+ ~~~
    + CategoryInfo          : ObjectNotFound: (tar:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

':
        exit status 1

Exit code 1

Here is the Git Bash output:

bosh create-env bosh.yml --state ./state.json -o virtualbox/cpi.yml -o virtualbox/outbound-network.yml -o bosh-lite.yml -o bosh-lite-runc.yml -o jumpbox-user.yml --vars-store ./creds.yml -v director_name="Bosh Lite Director" -v internal_ip=192.168.50.6 -v internal_gw=192.168.50.1 -v internal_cidr=192.168.50.0/24 -v outbound_network_name=NatNetwork
Extracting release 'C:\Users\dalbyb1\.bosh\downloads\a9cb72bf8fa9b8b4a7e80e1ef2bd61f4c008cf1d-37630c636a030454d55703cfdd495d733525353f':
  Extracting release:
    Shelling out to tar:
      Running command: 'powershell tar --no-same-owner -xzf C:\Users\dalbyb1\.bosh\downloads\a9cb72bf8fa9b8b4a7e80e1ef2bd61f4c008cf1d-37630c636a030454d55703cfdd495d733525353f -C C:\Users\dalbyb1\.bosh\installations\8861b2b8-be0a-4fbd-7b2a-9ef4b86e0a20\tmp\bosh-release899369503', stdout: '', stderr: 'tar (child): Cannot connect to C: resolve failed

gzip: stdin: unexpected end of file
/usr/bin/tar: Child returned status 128
/usr/bin/tar: Error is not recoverable: exiting now
':
        exit status 1

Exit code 1

It seems like in bosh is expecting there to be a cmdlet called tar in the Powershell environment, but I'm not sure how to set this up. Any ideas?

[Fydon]

Hi @bendalby82.

Windows support for bosh-cli is still a work in progress and I'm also looking into Windows support for the virtualbox-cpi. Please follow those issues for updates. For now unfortunately you'll need to use bosh-lite using Vagrant if you want to use BOSH on Windows, even though it is not recommended..

[jfmyers9]

Going to close this issue due to inactivity.

As mentioned, bosh-cli functionality on Windows is not fully supported as of the moment.

Also this appears to be related to the create-env command, if you have further questions or would like to continue this conversation, could you please open a new issue on the https://github.com/cloudfoundry/bosh-cli repository.

Thanks.