Before upgrading to Incus v6.16, everything was fine; after upgrading, the containers won't start

rubenreyes · August 29, 2025, 5:00pm

Hi! First, I couldn’t report this issue via GitHub because the options menu available there assumes a level of user expertise I’m still far from achieving. Second, a few minutes ago, before updating to Incus v6.16, everything was working correctly. Finally, I need help diagnosing and troubleshooting the issue.

I’m attaching console logs, with some platform context. I’m happy to hear any requests and suggestions.

soporte@ost-demo1:~$ incus start ct-minecserver
Error: Failed to start device "xwayland_socket": Please look in /var/log/incus/ct-minecserver/proxy.xwayland_socket.log
Try `incus info --show-log ct-minecserver` for more info
soporte@ost-demo1:~$ incus info --show-log ct-minecserver
Name: ct-minecserver
Description: 
Status: STOPPED
Type: container
Arquitectura: x86_64
Creado: 2025/08/22 15:24 -04
Last Used: 2025/08/29 12:29 -04

Snapshots:
+-------+----------------------+------------+----------+
| Name  |       Taken at       | Expires at | Stateful |
+-------+----------------------+------------+----------+
| snap0 | 2025/08/24 18:01 -04 |            | NO       |
+-------+----------------------+------------+----------+

Registro:


soporte@ost-demo1:~$ sudo nano /var/log/incus/ct-minecserver/proxy.xwayland_socket.log
Failed getting os.UserHomeDir(): $HOME is not definedFailed getting os.UserHomeDir(): $HOME is not definedStatus: Started
soporte@ost-demo1:~$ incus version
Versión del cliente: 6.16
Server version: 6.16
soporte@ost-demo1:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 25.04
Release:        25.04
Codename:       plucky
soporte@ost-demo1:~$ uname -a
Linux ost-demo1 6.13.12-061312-generic #202504200842 SMP PREEMPT_DYNAMIC Sun Apr 20 11:07:04 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
soporte@ost-demo1:~$

stgraber · August 29, 2025, 5:53pm

Try updating your system, we have pushed a fix for this earlier today.

It looks like a change in behavior with the newer Go version that’s causing this issue.

rubenreyes · August 29, 2025, 6:10pm

Like a charm! Hi, stgraber! Thank you so much. I’ve unwittingly become the first to devour the sweets, but I seem to love them because of how quickly they help me overcome my vertigo.

Solved! Just as you indicated:

soporte@ost-demo1:~$ apt list --upgradable 
fwupd/plucky-updates 2.0.13-1~25.04.1 amd64 [actualizable desde: 2.0.7-1]
incus-base/noble 1:6.16-ubuntu24.04-202508291536 amd64 [actualizable desde: 1:6.16-ubuntu24.04-202508290331]
incus-client/noble 1:6.16-ubuntu24.04-202508291536 amd64 [actualizable desde: 1:6.16-ubuntu24.04-202508290331]
incus-ui-canonical/noble 1:6.16-ubuntu24.04-202508291536 amd64 [actualizable desde: 1:6.16-ubuntu24.04-202508290331]
incus/noble 1:6.16-ubuntu24.04-202508291536 amd64 [actualizable desde: 1:6.16-ubuntu24.04-202508290331]
libfwupd3/plucky-updates 2.0.13-1~25.04.1 amd64 [actualizable desde: 2.0.7-1]
xdg-desktop-portal/plucky-updates 1.20.0+ds-2ubuntu1.1 amd64 [actualizable desde: 1.20.0+ds-2ubuntu1]
soporte@ost-demo1:~$ sudo apt full-upgrade 
Upgrading:                              
  incus  incus-base  incus-client  incus-ui-canonical

Not upgrading yet due to phasing:
  fwupd  libfwupd3  xdg-desktop-portal

Summary:
  Upgrading: 4, Installing: 0, Removing: 0, Not Upgrading: 3
  Download size: 151 MB
  Space needed: 9.862 kB / 437 GB available

Continue? [S/n] s
soporte@ost-demo1:~$ incus list ^ct-minecserver$
+----------------+---------+------------------------------+------+-----------+-----------+
|      NAME      |  STATE  |             IPV4             | IPV6 |   TYPE    | SNAPSHOTS |
+----------------+---------+------------------------------+------+-----------+-----------+
| ct-minecserver | RUNNING | 192.168.192.100 (zt6ntbnuo4) |      | CONTAINER | 1         |
|                |         | 10.0.1.100 (eth0)            |      |           |           |
+----------------+---------+------------------------------+------+-----------+-----------+
soporte@ost-demo1:~$

candlerb · August 30, 2025, 10:01am

I guess that is commit 060c33a7 in the zabbly/incus repo. But do you have a reference to the change in Go behaviour? I couldn’t find it.

stgraber · August 31, 2025, 7:01am

github.com/jaypipes/pcidb

Tiny regression when HOME isn't set

opened 10:02PM - 30 Aug 25 UTC

stgraber

We recently ran into a bit of a regression which one of our users managed to tra…ck down to a change to the pcidb package. https://github.com/lxc/incus/issues/2439 It looks like the old logic was handling a missing `HOME` env variable without triggering the error path, but now the new logic doesn't. We worked around it in packaging by setting HOME to /var/lib/incus, but this may still hit some of our users using packages from their distro where that logic would then need to be added by each individual packager. Any chance we could get the previous behavior restored (no error on HOME not being set)?

Turned out to be a change coming from one of our dependencies…