sprotheroe / vagrant-disksize

Vagrant plugin to resize disks in VirtualBox
MIT License
479 stars 51 forks source link

Plugin Not Triggering #43

Open jamiejackson opened 4 years ago

jamiejackson commented 4 years ago

This set up worked fine until I got a replacement laptop and put new versions of everything in place:

Mac Catalina 10.15.7 Vagrant 2.2.13 VirtualBox: 6.1.16

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vagrant.plugins = [
      "vagrant-disksize"
    ]
  config.vm.box = "ubuntu/bionic64"
  config.disksize.size = '60GB'
end

I don't see the usual resizing output among the logs:

jjackson@ICF2009653 vagrantexp % vagrant up
Vagrant has detected project local plugins configured for this
project which are not installed.

  vagrant-disksize
Install local plugins (Y/N) [N]: y
Installing the 'vagrant-disksize' plugin. This can take a few minutes...
Fetching vagrant-disksize-0.1.3.gem
Installed the plugin 'vagrant-disksize (0.1.3)'!

Vagrant has completed installing local plugins for the current Vagrant
project directory. Please run the requested command again.

###################################################

jjackson@ICF2009653 vagrantexp % vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/bionic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/bionic64' version '20201112.0.0' is up to date...
==> default: Setting the name of the VM: vagrantexp_default_1605652192162_53536
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 5.2.42
    default: VirtualBox Version: 6.1
==> default: Mounting shared folders...
    default: /vagrant => /private/tmp/vagrantexp

###################################################

jjackson@ICF2009653 vagrantexp % vagrant ssh | df -h
Filesystem      Size   Used  Avail Capacity iused      ifree %iused  Mounted on
/dev/disk1s5   466Gi   10Gi  414Gi     3%  488254 4881964626    0%   /
devfs          189Ki  189Ki    0Bi   100%     654          0  100%   /dev
/dev/disk1s1   466Gi   40Gi  414Gi     9%  517570 4881935310    0%   /System/Volumes/Data
/dev/disk1s4   466Gi  1.0Gi  414Gi     1%       1 4882452879    0%   /private/var/vm
map auto_home    0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/home
map -fstab       0Bi    0Bi    0Bi   100%       0          0  100%   /System/Volumes/Data/Network/Servers
psibre commented 4 years ago

Upstream issue: hashicorp/vagrant#12035

psibre commented 3 years ago

FWIW, this issue can be closed -- upgrading to Vagrant v2.2.14 resolves the regression.