pgwillia
commented
9 years ago Trying out Google Drive. A couple of blockers:
When I try to wget the url that I can download from in my browser, it redirects to a page which challenges for my password. I can see the same thing happening to vagrant box add.
vagrant box add centos6.5.json
==> box: Loading metadata for box 'centos6.5.json'
box: URL: file://C:/Development/workspace/testvagrantmetadata/centos6.5.json
==> box: Adding box 'ual/centos6.5' (v0.5.0) for provider: virtualbox
box: Downloading: https://doc-0k-8g-docs.googleusercontent.com/docs/securesc/xxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxx?h=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx&e=download
box:
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and try again. The
output from attempting to unpackage (if any):
bsdtar.EXE: Can't open <html>
x <html>
bsdtar.EXE: Can't open <head>
x <head>
bsdtar.EXE: Can't open </head>
x </head>
bsdtar.EXE: Can't open <body
x <body
bsdtar.EXE: Can't open <form
x <form
bsdtar.EXE: Can't open <input
x <input
bsdtar.EXE: Can't open <input
x <input
bsdtar.EXE: Can't open <input
x <input
bsdtar.EXE: Can't open <noscript>
x <noscript>
bsdtar.EXE: Can't open <p
x <p
bsdtar.EXE: Can't open <p
x <p
bsdtar.EXE: Can't open <input
x <input
bsdtar.EXE: Can't open </noscript>
x </noscript>
bsdtar.EXE: Can't open </form>
x </form>
bsdtar.EXE: Can't open </html>
x </html>
bsdtar.EXE: Error exit delayed from previous errors.
I figured out versioning for Vagrant boxes. In order to make this available to developers we need a http server which would serve a directory containing a centos6.5.json file and the .box files. We would need to update the centos6.5.json file whenever a .box file was added to the directory. The directory would look a lot like //libroot/ITS_Share/Tricia/vagrantboxes. The simple http server would challenge for developer credentials and forbid access if it didn't receive them.
You can check if the box you're using is outdated with vagrant box outdated. This can check if the box in your current Vagrant environment is outdated as well as any other box installed on the system.
Finally, you can update boxes with vagrant box update. This will download and install the new box. This will not magically update running Vagrant environments. If a Vagrant environment is already running, you'll have to destroy and recreate it to acquire the new updates in the box. The update command just downloads these updates locally.
[https://docs.vagrantup.com/v2/boxes/versioning.html]
Extension of #4 requested by @nnunn
@pbinkley do I have permission to create a private github repo for this purpose? The alternative is to work with the network and unix team to configure apache or similar to do this for us in a new or existing vm.