New issue by sbromberger on void-packages repository

https://github.com/void-linux/void-packages/issues/48356

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.11_1 x86_64 AuthenticAMD uptodate rFF

### Package(s) Affected

incus-0.4.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Migrated from a home-built version of incus to the new package (yay!) - but while void images start up with no problem, ubuntu ones (including new images) fail to start. I expected the ubuntu images to start up normally.

### Actual behaviour

Ubuntu images (based on `lunar`; possibly others) fail to start. There is no diagnostic information printed either with `-v`.

`--console` produces the following error:

```
[root@elemental beryllium]# incus start testub --console
To detach from the console, press: <ctrl>+a q
Error: Failed running forkconsole: "container is not running: \"testub\""
                                                                         Error: write /dev/pts/ptmx: file already closed
```

`-debug` produces the following output: https://gist.github.com/sbromberger/e6adcff70ab7e6fd0410055cfde09e69



### Steps to reproduce

1. `incus create images:ubuntu/lunar testub`
2. `incus start testub`
3. `incus ls testub`
4. Observe that status is `STOPPED`