vagrant debian/buster64 box failed (win10)

mat-twg commented 4 years ago

Hello! I got errors on init debian/buster64 box... Who knows what is wrong?

Console output

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'debian/buster64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'debian/buster64'
    default: URL: https://vagrantcloud.com/debian/buster64
==> default: Adding box 'debian/buster64' (v10.4.0) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/debian/boxes/buster64/versions/10.4.0/providers/virtualbox.box
Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
    default:
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and that enough disk space
is available and then try again.
The output from attempting to unpackage (if any):

x ./metadata.json: Cannot extract through symlink \\\\?\\C:\\Users\\mat\\.vagrant.d
x ./box.ovf: Cannot extract through symlink \\\\?\\C:\\Users\\mat\\.vagrant.d
x ./buster.vmdk: Cannot extract through symlink \\\\?\\C:\\Users\\mat\\.vagrant.d
x ./Vagrantfile: Cannot extract through symlink \\\\?\\C:\\Users\\mat\\.vagrant.d

Vagrant version

$ vagrant -v
Vagrant 2.2.9

Host operating system

os: windows 10
version: 1909
build: 18363.900

Guest operating system

debian/buster64

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.box = "debian/buster64"

  # 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"

  # 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

Actual behavior

The box failed to unpackage properly.

Steps to reproduce

vagrant init debian/buster64
vagrant up

jbonhag commented 4 years ago

Hi there,

Thanks for opening an issue with Vagrant! Is your home directory a symlink to another directory? It looks like that may be causing an issue.

Would you mind posting the output of vagrant up --debug as a Gist so we can investigate the issue further? Thanks!

mat-twg commented 4 years ago

Hi there,

Thanks for opening an issue with Vagrant! Is your home directory a symlink to another directory? It looks like that may be causing an issue.

Would you mind posting the output of vagrant up --debug as a Gist so we can investigate the issue further? Thanks!

Yes, it was simlink, and last year extract through symlinks works without any errors... I changed VAGRANT_HOME with command:

setx VAGRANT_HOME "X:/your/path" /M

Now works fine, thank you!

ghost commented 4 years ago

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.

hashicorp / vagrant