Re: 'vagrant up' does not seem to properly start 'debian/bookworm64'
Ok, issue found thanks to you!
$ dpkg -l | grep vagrant
ii vagrant:i386 1:2.2.9
i386 no description given
$ vagrant --version
Vagrant 2.2.9
$ which vagrant
/usr/bin/vagrant
$ gem list | grep vagrant
$
Let's have a look to vagrant package:
$ apt show vagrant
Package: vagrant
Version: 2.2.19+dfsg-1ubuntu1
Priority: optional
Section: universe/admin
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3.559 kB
Depends: libarchive-tools, curl, openssh-client, rsync, ruby,
ruby-bcrypt-pbkdf, ruby-childprocess, ruby-ed25519, ruby-erubi,
ruby-i18n, ruby-listen, ruby-log4r, ruby-mime-types, ruby-net-ssh,
ruby-net-sftp, ruby-net-scp, ruby-rexml, ruby-zip, ruby-vagrant-cloud
Recommends: vagrant-libvirt
Suggests: virtualbox (>= 4.0)
Breaks: virtualbox (>= 6.2)
Homepage: https://www.vagrantup.com
Ruby-Versions: all
Download-Size: 473 kB
APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy/universe amd64
Packages
Description: Tool for building and distributing virtualized development
environments
This package provides the tools to create and configure lightweight,
reproducible, and portable virtual environments.
.
Vagrant upstream uses Oracle’s VirtualBox by default to create its virtual
machines. On Debian, Vagrant will use libvirt/KVM by default as
VirtualBox is
not part of Debian main, but will use VirtualBox if it's installed.
$ apt show vagrant:i386
Package: vagrant:i386
Version: 1:2.2.9
Status: install ok installed
Priority: extra
Section: default
Maintainer: HashiCorp <support@hashicorp.com>
Installed-Size: 114 MB
Homepage: https://www.vagrantup.com/
License: unknown
Vendor: root@vagrant
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: no description given
So my issue, was that "vagrant:i386" was installed and not 'vagrant'. I
am not sure why (old vagrant instructions maybe?). Installing the
package "vagrant" uninstall "vagrant:i386" and fix my issue. Thanks a
lot Lucas!
On 03.08.23 11:27, Lucas Nussbaum wrote:
On 03/08/23 at 10:43 +0200, Olivier MARTIN wrote:
Thanks Lucas, it seems you found an interesting point to investigate.
Just for people who might end up in this thread, "jammy" is Ubuntu 22.04 and
not Ubuntu 20.04.
Ah yes, sorry, typo
To help us to narrow down the issue, I will not take short cut. I do not
have 'ruby-net-ssh'. Should I install it?
vagrant should depend on ruby-net-ssh. Are you not using the vagrant
package from Ubuntu?
If you installed it manually (using gem install), the same applies: you
need to update the 'net-ssh' gem to a version that supports OpenSSH from
bookworm.
Lucas
Reply to: