bosh-cli: [windows] bosh add-blobs failed

bosh add-blob C:\Projects\mything\bin\mything.zip mything/mything.zip
Tracking blob:
  Moving temp blob to blobs/:
    rename C:\Users\drnic\.bosh\tmp\track-blob603273339 C:\Projects\mything-boshrelease\blobs\mything\mything.zip: The process cannot access the file because it is being used by another process.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (10 by maintainers)

Most upvoted comments

Hi, I am also getting the same error. I am using cygwin on windows 7.

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. 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 Deployment manifest: ‘C:\BOSH\workspace\bosh-deployment\bosh.yml’ Deployment state: ‘./state.json’

Started validating Downloading release ‘bosh’… Finished (00:00:47) Validating release ‘bosh’… Failed (00:00:19) Failed validating (00:01:17)

←[31mExtracting release ‘.bosh\downloads\00408810832ec663212900fc4810385a230d4dbf-f262d1c35f3646a3f0394132f2705719c9d2bb6a’: Extracting release: Shelling out to tar: Running command: ‘powershell tar --no-same-owner -xzf .bosh\downloads\00408810832ec663212900fc4810385a230d4dbf-f262d1c35f3646a3f0394132f2705719c9d2bb6a -C .bosh\installations\2feb4a41-bbed-4492-62cc-fcea5af7db7a\tmp\bosh-release266833682’, stdout: ‘’, stderr: '/usr/bin/tar: .bosh\installations\002feb4a41-bbed-4492-62cc-fcea5af7db7a\tmp\bosh-release266833682: Cannot open: No such file or dir ectory /usr/bin/tar: Error is not recoverable: exiting now ': exit status 1←[0m

←[31mExit code 1←[0m

dawg2k on Nov 29, 2017

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 bosh-virtualbox-cpi to compile, create VMs and attach disks, but currently it is still failing before it completes the create-env command. You can see the changes to bosh-cli on this branch, although I’ll split those changes into different branches and create separate pull requests for some of the changes. The reason that I don’t think that all the changes should be applied is because I don’t think that using bash scripts built for Linux should be used on Windows. There different bash implementations on Windows, e.g. MSYS, Cygwin and Windows Subsystems for Linux, and each of those handling things differently to each other as well as being different to typical Linux distributions. For example they take different approaches as to how to reference the location of a file on a specific drive.

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 on Sep 20, 2017

@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 add-blobs to work. If we extend this issue to include problems with create-env then it is still open, as compilation doesn’t work yet, but rename will work with the next release.

Fydon on Sep 1, 2017