From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] incus images based on Ubuntu fail to start
Date: Wed, 24 Jan 2024 18:32:30 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48356@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
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`
next reply other threads:[~2024-01-24 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 17:32 sbromberger [this message]
2024-01-24 18:01 ` sbromberger
2024-01-24 18:14 ` sbromberger
2024-01-24 19:41 ` CameronNemo
2024-02-27 21:07 ` BikyAlex
2024-02-27 23:15 ` CameronNemo
2024-02-27 23:18 ` classabbyamp
2024-02-28 2:01 ` CameronNemo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48356@inbox.vuxu.org \
--to=sbromberger@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).