Experimental disk VAGRANT_EXPERIMENTAL="disks" not working as expected

[anfoss]

I want to run singularity through a VM in vagrant. I mounted it on a HDD as I need more than the default disk size.

As it seems pretty straightforward compared to manually change it with cfdisk and resize2fs I enabled the experimental mode and set up 150G

I appended to my .bash_profile

' VAGRANT_EXPERIMENTAL="disks"'

Vagrant version

Vagrant 2.3.0

Guest operating system

ubuntu-bionic64

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.
  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.disk :disk, size: "150GB", primary: true
  config.vm.box = "sylabs/singularity-3.5-ubuntu-bionic64"
  #config.disksize.size = '150GB'
  config.vm.box_version = "20191206.0.0"
  config.vm.box_check_update = false

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"
  config.vm.provision "file", source: "alphafold220_docker.tar", destination: "alphafold220_docker.tar"
  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

end

Expected behavior

There should be the 150 G assigned in the Vagrantfile

Actual behavior

Still has the default 20

Steps to reproduce

vagrant up
vagrant provision

vagrant ssh
sudo cfdisk /dev/sda 

Device Boot Start End Sectors Size Id Type

/dev/sda1 * 2048 41940991 41938944 20G 8e Linux LVM

During creation of the VM it seems that the flag is recognized and that the disk somehow was resized.

==> vagrant: You have requested to enabled the experimental flag with the following features:
==> vagrant: 
==> vagrant: Features:  disks
==> vagrant: 
==> vagrant: Please use with caution, as some of the features may not be fully
==> vagrant: functional yet.
==> default: Configuring storage mediums...
    default: Disk 'vagrant_primary' needs to be resized. Resizing disk...

[chrisroberts]

Hi there,

I believe the issue you are encountering is that you need to export the environment variable:

export VAGRANT_EXPERIMENTAL="disks"