Open viktor76525 opened 11 months ago
This still occurs with vagrant v2.4.0, Debian unstable host, simply running vagrant without arguments.
Tried the busybox (static) suggestion
avoids awk symbol lookup error. Unfortunately I also run into a symbol lookup error (before and after this workaround test) so I can´t say that this worked explicitly to a useful conclusion, but might be useful in a pinch otherwise…
Stderr: /usr/lib/virtualbox/VBoxManage: symbol lookup error: /lib/x86_64-linux-gnu/libcurl-gnutls.so.4: undefined symbol: libssh2_session_set_read_timeout
fwiw and ymmv
Awk is used by Vagrant but is not included in the App Image, therefore it depends on the system's awk to be compatible with your provided library.
Debug output
While doing
vagrant up
Issue is pretty clear and can be seen by setting the library path inside the extracted App Image.
Expected behavior
Vagrant should include the awk binary in the AppImage, maybe use busybox? Or at least reset the library path before running commands which are expected to be on the system.
Actual behavior
Vagrant does not provide the awk binary, it assumes the system awk binary is compatible with the provided libreadline.so.
Reproduction information
Vagrant version
2.3.4 and 2.3.7 tried. Downloaded from the AMD64 link on the downloads page https://www.vagrantup.com/downloads.html.
Host operating system
Gentoo Linux
Guest operating system
Ubuntu
Steps to reproduce
vagrant up
in setup repo.Vagrantfile