Created
November 10, 2020 02:47
-
-
Save xmunoz/7fae9f013b268e2032139ac3a238c5d8 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| INFO interface: output: Machine booted and ready! | |
| INFO interface: output: ==> permanent: Machine booted and ready! | |
| ==> permanent: Machine booted and ready! | |
| INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00007f6994813148> | |
| INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00007f6994eb1a68> | |
| INFO warden: Calling IN action: #<Vagrant::Action::Builtin::IsEnvSet:0x00007f6994f9e728> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::IsEnvSet:0x00007f6994f9e728> | |
| INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x00007f6995237278> | |
| INFO warden: Calling IN action: #<Proc:0x00007f69954056e0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling IN action: #<Vagrant::Action::Builtin::CloudInitWait:0x00007f6995236f80> | |
| INFO warden: Calling IN action: #<Proc:0x00007f69952aedc8@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::Customize:0x00007f69948130a8> | |
| INFO warden: Calling IN action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckGuestAdditions:0x00007f6994813058> | |
| INFO interface: output: Checking for guest additions in VM... | |
| INFO interface: output: ==> permanent: Checking for guest additions in VM... | |
| ==> permanent: Checking for guest additions in VM... | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "guestproperty", "get", "da0cf8c6-c6cd-441e-b435-20db68537c72", "/VirtualBox/GuestAdd/Version"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "da0cf8c6-c6cd-441e-b435-20db68537c72", "--machinereadable"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO interface: detail: The guest additions on this VM do not match the installed version of | |
| VirtualBox! In most cases this is fine, but in rare cases it can | |
| prevent things such as shared folders from working properly. If you see | |
| shared folder errors, please make sure the guest additions within the | |
| virtual machine match the version of VirtualBox you have installed on | |
| your host and reload your VM. | |
| Guest Additions Version: 5.2.0 r68940 | |
| VirtualBox Version: 6.1 | |
| INFO interface: detail: permanent: The guest additions on this VM do not match the installed version of | |
| permanent: VirtualBox! In most cases this is fine, but in rare cases it can | |
| permanent: prevent things such as shared folders from working properly. If you see | |
| permanent: shared folder errors, please make sure the guest additions within the | |
| permanent: virtual machine match the version of VirtualBox you have installed on | |
| permanent: your host and reload your VM. | |
| permanent: | |
| permanent: Guest Additions Version: 5.2.0 r68940 | |
| permanent: VirtualBox Version: 6.1 | |
| permanent: The guest additions on this VM do not match the installed version of | |
| permanent: VirtualBox! In most cases this is fine, but in rare cases it can | |
| permanent: prevent things such as shared folders from working properly. If you see | |
| permanent: shared folder errors, please make sure the guest additions within the | |
| permanent: virtual machine match the version of VirtualBox you have installed on | |
| permanent: your host and reload your VM. | |
| permanent: | |
| permanent: Guest Additions Version: 5.2.0 r68940 | |
| permanent: VirtualBox Version: 6.1 | |
| INFO warden: Calling IN action: #<Proc:0x00007f6994868a80@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling IN action: #<Proc:0x00007f69944da670@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling IN action: #<Proc:0x0000000002412b50@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling IN action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x0000000002dde878> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::CommandUp::StoreBoxMetadata:0x0000000002dde878> | |
| INFO warden: Calling OUT action: #<Proc:0x0000000002412b50@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f69944da670@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f6994868a80@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::CheckGuestAdditions:0x00007f6994813058> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Customize:0x00007f69948130a8> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f69952aedc8@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::CloudInitWait:0x00007f6995236f80> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f69954056e0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00007f6994813148> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::WaitForCommunicator:0x00007f6994813198> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Customize:0x00007f69948131e8> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Boot:0x00007f6994813238> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Customize:0x00007f6994813288> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Disk:0x00007f69947e2a98> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::CleanupDisks:0x00007f69947a3320> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f6994f80250@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::CloudInitSetup:0x00007f6994f10450> | |
| INFO warden: Calling OUT action: #<Proc:0x00007f69950d1118@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:126 (lambda)> | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Call:0x00007f69947a3460> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::SaneDefaults:0x00007f6994778cb0> | |
| INFO set_hostname: `allow_hosts_modification` set to false. Hosts modification has been disabled, skiping changing hostname. | |
| INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::SetHostname:0x00007f699469b090> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::ForwardPorts:0x00007f699469b0e0> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::NetworkFixIPv6:0x00007f69941ea9d8> | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "da0cf8c6-c6cd-441e-b435-20db68537c72", "--machinereadable"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO interface: info: Configuring and enabling network interfaces... | |
| INFO interface: info: ==> permanent: Configuring and enabling network interfaces... | |
| ==> permanent: Configuring and enabling network interfaces... | |
| INFO ssh: SSH is ready! | |
| INFO ssh: Execute: (sudo=false) | |
| INFO guest: Execute capability: configure_networks [#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>, [{:type=>:static, :adapter_ip=>"192.168.33.1", :ip=>"192.168.33.10", :netmask=>"255.255.255.0", :auto_config=>true, :interface=>1}]] (debian) | |
| INFO ssh: SSH is ready! | |
| INFO ssh: Execute: (sudo=false) | |
| INFO guest: Execute capability: network_interfaces [#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>] (debian) | |
| INFO ssh: Execute: /sbin/ip -o -0 addr | grep -v LOOPBACK | awk '{print $2}' | sed 's/://' (sudo=true) | |
| INFO ssh: Execute: cat /proc/net/dev | grep -E '^[a-z0-9 ]+:' | awk '{print $1}' | sed 's/://' (sudo=true) | |
| INFO ssh: Execute: /sbin/ip -o -0 addr | grep LOOPBACK | awk '{print $2}' | sed 's/://' (sudo=true) | |
| INFO ssh: Execute: ps -o comm= 1 | grep systemd (sudo=true) | |
| INFO ssh: Execute: command -v netplan (sudo=false) | |
| INFO ssh: Execute: systemctl -q is-active systemd-networkd.service (sudo=true) | |
| INFO ssh: Execute: mkdir -p "/tmp" (sudo=false) | |
| INFO ssh: Execute: /sbin/ifdown 'eth1' || true | |
| /sbin/ip addr flush dev 'eth1' | |
| # Remove any previous network modifications from the interfaces file | |
| sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre | |
| sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post | |
| cat \ | |
| /tmp/vagrant-network-interfaces.pre \ | |
| /tmp/vagrant-network-entry \ | |
| /tmp/vagrant-network-interfaces.post \ | |
| > /etc/network/interfaces | |
| rm -f /tmp/vagrant-network-interfaces.pre | |
| rm -f /tmp/vagrant-network-entry | |
| rm -f /tmp/vagrant-network-interfaces.post | |
| /sbin/ifup 'eth1' (sudo=true) | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::Network:0x00007f6994326a40> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::ClearNetworkInterfaces:0x00007f6994326a68> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::SetDefaultNICType:0x00007f69944db520> | |
| INFO warden: Calling OUT action: #<VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings:0x00007f69943a3950> | |
| INFO synced_folders: Invoking synced folder enable: virtualbox | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "guestproperty", "get", "da0cf8c6-c6cd-441e-b435-20db68537c72", "/VirtualBox/GuestInfo/OS/Product"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO interface: output: Mounting shared folders... | |
| INFO interface: output: ==> permanent: Mounting shared folders... | |
| ==> permanent: Mounting shared folders... | |
| INFO interface: detail: /data/www/api => /home/user/workspace/permanent/development/api | |
| INFO interface: detail: permanent: /data/www/api => /home/user/workspace/permanent/development/api | |
| permanent: /data/www/api => /home/user/workspace/permanent/development/api | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "da0cf8c6-c6cd-441e-b435-20db68537c72", "--machinereadable"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "da0cf8c6-c6cd-441e-b435-20db68537c72", "--machinereadable"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO ssh: SSH is ready! | |
| INFO ssh: Execute: (sudo=false) | |
| INFO guest: Execute capability: mount_virtualbox_shared_folder [#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>, "data_www_api", "/data/www/api", {:owner=>"vagrant", :group=>"www-data", :guestpath=>"/data/www/api", :hostpath=>"/home/user/workspace/permanent/development/api", :disabled=>false, :__vagrantfile=>true, :plugin=>#<VagrantPlugins::ProviderVirtualBox::SyncedFolder:0x00007f69954a3a98 @cap_logger=#<Log4r::Logger:0x00007f69954a25f8 @fullname="vagrant::capability_host::vagrantplugins::providervirtualbox::syncedfolder", @outputters=[], @additive=true, @name="syncedfolder", @path="vagrant::capability_host::vagrantplugins::providervirtualbox", @parent=#<VagrantLogger:0x00000000023f98a8 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x0000000001a7bf60 @mon_mutex=#<Thread::Mutex:0x0000000001a822c0>, @mon_mutex_owner_object_id=13885360, @mon_owner=nil, @mon_count=0, @name="stderr", @level=0, @formatter=#<Vagrant::Util::LoggingFormatter:0x0000000001ef7968 @formatter=#<Log4r::BasicFormatter:0x0000000001eed418 @depth=7>>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x00000000023f9498 @level=0, @outputters=[]>, @level=2, @trace=false>, @level=2, @trace=false>, @cap_host_chain=[[:virtualbox, #<VagrantPlugins::ProviderVirtualBox::SyncedFolder:0x00007f69954e7720>]], @cap_args=[#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>], @cap_caps={:virtualbox=>#<Vagrant::Registry:0x00007f69954a2850 @items={:mount_options=>#<Proc:0x00000000022ade68@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/plugin.rb:72>, :mount_type=>#<Proc:0x00000000022add00@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/plugin.rb:77>}, @results_cache={}>, :smb=>#<Vagrant::Registry:0x00007f69954a27b0 @items={:default_fstab_modification=>#<Proc:0x0000000001feec18@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:26>, :mount_options=>#<Proc:0x0000000001feeba0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:31>, :mount_name=>#<Proc:0x0000000001feeab0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:36>, :mount_type=>#<Proc:0x0000000001fee9e8@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:41>}, @results_cache={}>}>}] (debian) | |
| INFO syncedfolder: Execute capability: mount_type [#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>] (virtualbox) | |
| INFO syncedfolder: Execute capability: mount_options [#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>, "data_www_api", "/data/www/api", {:owner=>"vagrant", :group=>"www-data", :guestpath=>"/data/www/api", :hostpath=>"/home/user/workspace/permanent/development/api", :disabled=>false, :__vagrantfile=>true, :plugin=>#<VagrantPlugins::ProviderVirtualBox::SyncedFolder:0x00007f69954a3a98 @cap_logger=#<Log4r::Logger:0x00007f69954a25f8 @fullname="vagrant::capability_host::vagrantplugins::providervirtualbox::syncedfolder", @outputters=[], @additive=true, @name="syncedfolder", @path="vagrant::capability_host::vagrantplugins::providervirtualbox", @parent=#<VagrantLogger:0x00000000023f98a8 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x0000000001a7bf60 @mon_mutex=#<Thread::Mutex:0x0000000001a822c0>, @mon_mutex_owner_object_id=13885360, @mon_owner=nil, @mon_count=0, @name="stderr", @level=0, @formatter=#<Vagrant::Util::LoggingFormatter:0x0000000001ef7968 @formatter=#<Log4r::BasicFormatter:0x0000000001eed418 @depth=7>>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x00000000023f9498 @level=0, @outputters=[]>, @level=2, @trace=false>, @level=2, @trace=false>, @cap_host_chain=[[:virtualbox, #<VagrantPlugins::ProviderVirtualBox::SyncedFolder:0x00007f69954e7720>]], @cap_args=[#<Vagrant::Machine: permanent (VagrantPlugins::ProviderVirtualBox::Provider)>], @cap_caps={:virtualbox=>#<Vagrant::Registry:0x00007f69954a2850 @items={:mount_options=>#<Proc:0x00000000022ade68@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/plugin.rb:72>, :mount_type=>#<Proc:0x00000000022add00@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/plugin.rb:77>}, @results_cache={:mount_type=>VagrantPlugins::ProviderVirtualBox::Cap::MountOptions, :mount_options=>VagrantPlugins::ProviderVirtualBox::Cap::MountOptions}>, :smb=>#<Vagrant::Registry:0x00007f69954a27b0 @items={:default_fstab_modification=>#<Proc:0x0000000001feec18@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:26>, :mount_options=>#<Proc:0x0000000001feeba0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:31>, :mount_name=>#<Proc:0x0000000001feeab0@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:36>, :mount_type=>#<Proc:0x0000000001fee9e8@/opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/synced_folders/smb/plugin.rb:41>}, @results_cache={}>}>}] (virtualbox) | |
| INFO ssh: Execute: id -u vagrant (sudo=false) | |
| INFO ssh: Execute: getent group www-data (sudo=false) | |
| INFO ssh: Execute: mkdir -p /data/www/api (sudo=true) | |
| INFO ssh: Execute: mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api (sudo=true) | |
| INFO ssh: Execute: mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api (sudo=true) | |
| INFO retryable: Retryable exception raised: #<Vagrant::Errors::VirtualBoxMountFailed: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| > | |
| INFO ssh: Execute: mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api (sudo=true) | |
| INFO retryable: Retryable exception raised: #<Vagrant::Errors::VirtualBoxMountFailed: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| > | |
| INFO ssh: Execute: mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api (sudo=true) | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00007f6994813148> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00007f69947a3460> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x0000000002642628> | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00007f69944da760> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000000024134d8> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000002ddea30> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000002cd7f88> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Calling recover: #<VagrantPlugins::ProviderVirtualBox::Action::Import:0x00007f6994195000> | |
| INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "showvminfo", "da0cf8c6-c6cd-441e-b435-20db68537c72", "--machinereadable"] | |
| INFO subprocess: Command not in installer, restoring original environment... | |
| INFO warden: Recovery complete. | |
| INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000002cb0280> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| ERROR warden: Error occurred: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO environment: Released process lock: machine-action-3be5c9470e4a3f74f8937823bdc7bb0c | |
| INFO environment: Running hook: environment_unload | |
| INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00007f6995726f90> | |
| ERROR vagrant: Vagrant experienced an error! Details: | |
| ERROR vagrant: #<Vagrant::Errors::VirtualBoxMountFailed: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| > | |
| ERROR vagrant: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| ERROR vagrant: /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/communicators/ssh/communicator.rb:268:in `execute' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/communicators/ssh/communicator.rb:278:in `sudo' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/guests/linux/cap/mount_virtualbox_shared_folder.rb:45:in `block in mount_virtualbox_shared_folder' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/retryable.rb:17:in `retryable' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/guests/linux/cap/mount_virtualbox_shared_folder.rb:44:in `mount_virtualbox_shared_folder' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/capability_host.rb:111:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/capability_host.rb:111:in `capability' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/guest.rb:43:in `capability' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/synced_folder.rb:53:in `block in enable' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/synced_folder.rb:37:in `each' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/synced_folder.rb:37:in `enable' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/synced_folders.rb:93:in `block in call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/synced_folders.rb:90:in `each' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/synced_folders.rb:90:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/delayed.rb:19:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:52:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/env_set.rb:19:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/provision.rb:80:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/set_name.rb:50:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/clean_machine_folder.rb:26:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/call.rb:53:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/call.rb:53:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/call.rb:53:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/box_check_outdated.rb:92:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/config_validate.rb:25:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/env_set.rb:19:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/match_mac_address.rb:22:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/discard_state.rb:15:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/import.rb:46:in `clone' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/import.rb:11:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/prepare_clone_snapshot.rb:32:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/import_master.rb:36:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/customize.rb:40:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/call.rb:53:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/config_validate.rb:25:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/handle_box.rb:56:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:127:in `block in finalize_action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builtin/call.rb:53:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/warden.rb:48:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/builder.rb:149:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `block in run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/util/busy.rb:19:in `busy' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/action/runner.rb:89:in `run' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/machine.rb:246:in `action_raw' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/machine.rb:215:in `block in action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/environment.rb:613:in `lock' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/machine.rb:201:in `call' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/machine.rb:201:in `action' | |
| /opt/vagrant/embedded/gems/2.2.13/gems/vagrant-2.2.13/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run' | |
| INFO interface: error: Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| Vagrant was unable to mount VirtualBox shared folders. This is usually | |
| because the filesystem "vboxsf" is not available. This filesystem is | |
| made available via the VirtualBox Guest Additions and kernel module. | |
| Please verify that these guest additions are properly installed in the | |
| guest. This is not a bug in Vagrant and is usually caused by a faulty | |
| Vagrant box. For context, the command attempted was: | |
| mount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api | |
| The error output from the command was: | |
| : No such device | |
| INFO interface: Machine: error-exit ["Vagrant::Errors::VirtualBoxMountFailed", "Vagrant was unable to mount VirtualBox shared folders. This is usually\nbecause the filesystem \"vboxsf\" is not available. This filesystem is\nmade available via the VirtualBox Guest Additions and kernel module.\nPlease verify that these guest additions are properly installed in the\nguest. This is not a bug in Vagrant and is usually caused by a faulty\nVagrant box. For context, the command attempted was:\n\nmount -t vboxsf -o uid=1000,gid=33 data_www_api /data/www/api\n\nThe error output from the command was:\n\n: No such device\n"] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment