You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use the vagrant builder. I achieve creating a new image out of an existing one in my example. But the image created seems unusable: When creating a new box out of the new image, with vagrant up, vagrant cannot ssh: Remote connection disconnect ...
I tried generic/debian10 and generic/debian9 as base images.
Romainj1
changed the title
Builder vagrant with libvirt: Remote connection disconnect. to a box made from the packer-built image.
Builder vagrant with libvirt: "Remote connection disconnect" error to connect to a box made from the packer-built image.
Nov 20, 2021
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.
Overview of the Issue
I am trying to use the vagrant builder. I achieve creating a new image out of an existing one in my example. But the image created seems unusable: When creating a new box out of the new image, with
vagrant up
, vagrant cannot ssh:Remote connection disconnect
...I tried
generic/debian10
andgeneric/debian9
as base images.Reproduction Steps
Run:
Then as the doc mentions:
Everything works as expected, until:
Where i am getting:
until it timeouts
Packer version
Simplified Packer Template
Json template:
Operating system and Environment details
$ uname -a Linux rjr-port 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye $ vagrant --version Vagrant 2.2.19 $ virsh --version 7.0.0 $ libvirtd --version libvirtd (libvirt) 7.0.0
The text was updated successfully, but these errors were encountered: