Skip to content
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

Vagrant box add fail when the box is on another drive #6495

Closed
chevdor opened this issue Nov 6, 2015 · 4 comments
Closed

Vagrant box add fail when the box is on another drive #6495

chevdor opened this issue Nov 6, 2015 · 4 comments

Comments

@chevdor
Copy link

chevdor commented Nov 6, 2015

OS: Windows 10

c:>vagrant box add test d:\vagrant-images\win10ent.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'test' (v0) for provider:
    box: Unpacking necessary files from: file://d:/vagrant-images/win10ent.box
    box:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Couldn't open file /vagrant-images/win10ent.box

I copy the folder d:\vagrant-images to c:\vi and try the same thing again:

c:>vagrant box add test c:\vi\win10ent.box
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'test' (v0) for provider:
    box: Unpacking necessary files from: file://c:/vi/win10ent.box
    box: Progress: 100% (Rate: 453M/s, Estimated time remaining: --:--:--)
==> box: Successfully added box 'test' (v0) for 'virtualbox'!
@dragon788
Copy link
Contributor

@chevdor Can you perform this operation with the debug log enabled? I'd be really interested to see what the actual error message that was thrown looks like.
We use the VAGRANT_HOME environment variable to add boxes via metadata URL on C:\D:\E: drives and haven't had any trouble. I've also downloaded box files to a secondary disk and added them to a VAGRANT_HOME located on my primary disk, so I'm not sure what is causing the issue.

@chrisroberts
Copy link
Member

@chevdor If this is still an issue, can you please provide debug output of the error? Thanks!

@chrisroberts
Copy link
Member

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄

@ghost
Copy link

ghost commented Apr 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants