Trouble with debian/13 vm

Incus
1

In creating a debian vm, i ran into trouble with debian/13:

~# incus version
Client version: 6.19.1

~# incus launch images:debian/13 otbr-vm --vm -c limits.cpu=2 -c limits.memory=2GiB --storage zpool4 --profile default --profile lan-
bridge
Launching otbr-vm
~# incus exec otbr-vm – bash
Error: websocket: bad handshake

~# incus launch images:debian/12 otbr-vm --vm -c limits.cpu=2 -c limits.memory=2GiB --storage zpool4 --profile default --profile lan-
bridge
Launching otbr-vm
~# incus exec otbr-vm – bash
root@otbr-vm:~# passwd
New password:

Launching a remote console worked but, from what I understand, there’s no way to log-in before the root password has been set, which can only be accomplished using incus exec.

Is this the same issue as :Incus exec failing for vms with a websocket: bad handshake ?

If it is in fact a problem with how debian/13 was packaged, how do I communicate with the person who packaged it to inform them of the problem?

I could install debian/13 from an iso, which would allow me to create a log-in and ultimately ssh into the vm but, based on my experience with opensuse tumbleweed, I might very well run into the same problem with accessing the vm from incus.

jan erik

2

Hi Jan.

I was not able to reproduce your issue. The debian images work for me and I don’t get a websocket error.

My client version is 6.0.4 and my server version is 6.21. What is your server version?

3

It is now working for me. I don’t know what caused the temporary problem. I had rebooted the host os (fedora 43) and restarted incus. Going back through the events, it seems there was something odd happening with accessing incus as a regular user:

~# incus version
Client version: 6.19.1
Server version: unreachable
~# sudo -i
[sudo] password for k:
root@fedora:~# incus version
Client version: 6.19.1
Server version: 6.19.1
root@fedora:~# exit
~# incus version
Client version: 6.19.1
Server version: 6.19.1

At any rate, I can’t reproduce what happened earlier.

Thanks @jarrodu for looking into it.

4

I think it’s a known issue on Fedora, they tracked it. So it’s not the way the debian image was packaged but the incus package on Fedora.

https://bodhi.fedoraproject.org/updates/FEDORA-2025-ba21fcf444

2 Likes
5

@A2va is correct, I believe.

I have two Incus servers, one hosted on Ubuntu24 and one on my Fedora43 desktop.

Creating a Fedora43 VM on the Fedora desktop results in a vm that I can’t connect to

kees@racer:~$ incus shell forgejo-runner-3
Error while executing alias expansion: incus exec forgejo-runner-3 -- su -l
Error: websocket: bad handshake

Creating the same vm on the Ubuntu server. There I can connect without a problem.