You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.
Weirdest things is, once inside a box (debian/contrib-jessie64 (virtualbox, 8.10.0) but also ole/jessie64 (virtualbox, 0.2.2) in my case), apt-get upgrade gives the "not enough free space"-message, but aptitude upgrade will work OK and uses the cache...
Disabling both nfs and the mount_options for the plugin in the Vagrantfile makes things work (again).
Now I wonder: is this a Vagrant-, a macOS, a Debian-box (since for example ubuntu/xenial64 seems unaffected) or plugin-issue?
The text was updated successfully, but these errors were encountered:
Hey, sorry for the silence here but this project is looking for maintainers 😅
As per #193, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋
Ever since I'm on macOS 10.13 High Sierra APFS and using Vagrant 2.0.x I'm getting
when running
vagrant up
. Needles to say the disk is far from full:Weirdest things is, once inside a box (
debian/contrib-jessie64 (virtualbox, 8.10.0)
but alsoole/jessie64 (virtualbox, 0.2.2)
in my case),apt-get upgrade
gives the "not enough free space"-message, butaptitude upgrade
will work OK and uses the cache...Disabling both
nfs
and themount_options
for the plugin in theVagrantfile
makes things work (again).Now I wonder: is this a Vagrant-, a macOS, a Debian-box (since for example
ubuntu/xenial64
seems unaffected) or plugin-issue?The text was updated successfully, but these errors were encountered: