FS#56313 - [vagrant] Unable to run Vagrant after full system update (easy fix included)
Attached to Project:
Community Packages
Opened by Alexander Nye (anye) - Monday, 13 November 2017, 14:11 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 04 July 2018, 16:14 GMT
Opened by Alexander Nye (anye) - Monday, 13 November 2017, 14:11 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 04 July 2018, 16:14 GMT
|
Details
After latest `pacman -Syyu`, with updates from Sunday,
November 12th, 2017:
`vagrant-substrate` was replaced with https://www.archlinux.org/packages/community/x86_64/vagrant/ After which I started getting the following error when attempting to run `vagrant up`: `Exec error: fork/exec /opt/vagrant/embedded/bin/ruby: no such file or directory` This lead me to this prior, similar bug report: https://github.com/hashicorp/vagrant/issues/1559 I was able to fix the bug myself when I saw that `/opt/vagrant/embedded/bin` did not exist, created that directory, and created a symlink to my system ruby inside of it: `sudo ln -T $(which ruby) /opt/vagrant/embedded/bin/ruby` |
This task depends upon
Closed by Jonathan Steel (jsteel)
Wednesday, 04 July 2018, 16:14 GMT
Reason for closing: Works for me
Wednesday, 04 July 2018, 16:14 GMT
Reason for closing: Works for me
but i have other problem when attempting to run 'vagrant box update':
There was an error while downloading the metadata for this box.
The error message is shown below:
error setting certificate verify locations:
CAfile: /opt/vagrant/embedded/cacert.pem
CApath: none
I'd appreciate your help
which vagrant
vagrant --version
/usr/bin/vagrant
▶ vagrant --version
Vagrant 2.0.1
Vagrant file:
# -*- mode: ruby -*-
# vi: set ft=ruby :
# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "bento/centos-7.2"
config.vm.box_check_update = false
config.vm.provider "virtualbox" do |vb|
vb.gui = false
vb.memory = 8192
vb.cpus = 2
vb.customize ["modifyvm", :id, "--cpuexecutioncap", "80"]
end
end
Maybe the original reporter has anything more useful to add.
Vagrant 2.0.1
Plugins:
vagrant-librarian-chef-nochef (0.2.0)
vagrant-vbguest (0.15.0)
Vagrantfile below this line
--------------------------------
# -*- mode: ruby -*-
VAGRANTFILE_API_VERSION = '2'
REQUIRED_PLUGINS = ['vagrant-vbguest']
REQUIRED_PLUGINS.reject {|plugin| Vagrant.has_plugin? plugin}.each do|plugin|
if not system "vagrant plugin install #{plugin}"
abort "could not install #{plugin}"
end
end
Vagrant.configure VAGRANTFILE_API_VERSION do|config|
config.vm.box = 'ubuntu/trusty64'
config.vm.provider :virtualbox do|virtualbox|
virtualbox.customize ['modifyvm', :id, '--memory', '2048']
end
config.vm.network :forwarded_port, guest: 3000, host: 3000
config.vm.provision :chef_solo do|chef|
chef.cookbooks_path = %w[cookbooks]
chef.add_recipe 'aae::setup'
end
end
`uname -a` -> `Linux absurd-reckonings 4.14.0-1-MANJARO #1 SMP PREEMPT Wed Nov 1 18:24:41 UTC 2017 x86_64 GNU/Linux`
Name : vagrant
Version : 2.0.1-1
Description : Build and distribute virtualized development environments
Architecture : x86_64
URL : https://vagrantup.com
Licenses : MIT
Groups : None
Provides : None
Depends On : curl libarchive libssh2 libxml2 libxslt rsync ruby xz
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : vagrant-substrate
Replaces : vagrant-substrate
Installed Size : 26,23 MiB
Packager : Jonathan Steel <jsteel@archlinux.org>
Build Date : vie 03 nov 2017 09:51:46 -03
Install Date : lun 13 nov 2017 14:58:25 -03
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
If you create an Arch VM and can replicate the problem there I'd be happy to look into it further, but I think you'll find it's OK.
For reference https://forum.manjaro.org/t/stable-update-2017-11-12-kernels-plasma5-deepin-cinnamon-end-of-life-for-32bit-support/34635/43.
Also, thank you!
Every `vagrant` command (even `--version`) fails with the missing error `Exec error: fork/exec /opt/vagrant/embedded/bin/ruby: no such file or directory`.
PRETTY_NAME="Arch Linux"
ID=arch
ID_LIKE=archlinux
ANSI_COLOR="0;36"
HOME_URL="https://www.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"