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

Dependent on C: drive #48

Closed
caliskanfurkan opened this issue Jan 21, 2018 · 3 comments
Closed

Dependent on C: drive #48

caliskanfurkan opened this issue Jan 21, 2018 · 3 comments

Comments

@caliskanfurkan
Copy link

caliskanfurkan commented Jan 21, 2018

  • Operating System Version: W10
  • Provider (VirtualBox/VMWare): Virtualbox
  • Vagrant Version: 2.0.1
  • Packer Version: 1.1.3
  • Is the issue reproducible or intermittent? Yes

Installation on Windows 10 is heavly depends on (free-space) of C drive. Since a lot of users use C:\ only for Windows (SSD) and D:\ for general purpose, this can be optional for a default user. I tried a lot of hacks to make it work. (I installed all tools and install scripts on D, still uses C for VMs etc like C:\Users\username...)

PS: Can be done defining VAGRANT_HOME to D:\etc_directory

@clong
Copy link
Owner

clong commented Jan 23, 2018

@Ozirus Thanks for reporting! I can add that info to the README.md FAQ if that's what you're looking for here.

@clong
Copy link
Owner

clong commented Jan 23, 2018

Added to README.md in #50 under Troubleshooting/FAQ

@clong clong closed this as completed Jan 23, 2018
@caliskanfurkan
Copy link
Author

caliskanfurkan commented Jan 23, 2018

Thanks. Virtualbox default home directory can also be mentioned in document if you wish since by default VM's are also created again in C:\Users<username>\Virtualbox VMs\ etc. in Windows

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants