Your message dated Wed, 19 Mar 2025 23:24:14 +0000
with message-id <[email protected]>
and subject line Re: incus do not start anymore
has caused the Debian Bug report #1100842,
regarding incus do not start anymore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1100842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100842
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: incus
Version: 6.0.3-4~bpo12+1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
the new version of incus do not start anymore.
I found a workaround to solve the problem.
What I have found:
$ systemctl status incus-agent.service
return an error:
systemd[1]: incus-agent.service - Incus - agent was skipped because of an unmet
condition check
(ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.incus).
I see that the incus package has been removed
$ dpkg -l | grep incus
rc incus 6.0.3-2~bpo12+1
ii incus-agent 6.0.3-4~bpo12+1
ii incus-client 6.0.3-4~bpo12+1
ii incus-tools 6.0.3-2~bpo12+1
I don't have found any solution searching this problem.
So I tryied to insall incus
# apt install incus
[...]
The following packages have unmeet dependency: <- note I try to
translate from italian.
incus : Depend: qemu-system-x86 (>= 1:8.0) but version 1:7.2+dfsg-7+deb12u12
has been installing
So I added the backport repo in /etc/apt/sources.list adding the
following:
deb https://deb.debian.org/debian bookworm-backports main non-free contrib
non-free-firmware
and then installing the incus package
# apt install -t bookworm-backports incus incus-extra
and then starting the daemon:
# systemctl start incus-agent.service
now incus work
Ciao
Davide
-- System Information:
Debian Release: 12.10
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500,
'proposed-updates-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-32-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages incus depends on:
ii incus-agent 6.0.3-4~bpo12+1
ii incus-base 6.0.3-4~bpo12+1
ii qemu-system-x86 1:9.2.2+ds-1~bpo12+1
ii swtpm 0.7.1-1.3
incus recommends no packages.
Versions of packages incus suggests:
ii gdisk 1.0.9-2.1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Davide,
There are a couple things rolled into this bug report, which I'll
cover below:
On Wed, 19 Mar 2025 13:03:04 +0100 Davide Prina <[email protected]> wrote:
> Dear Maintainer,
>
> the new version of incus do not start anymore.
> I found a workaround to solve the problem.
>
> What I have found:
>
> $ systemctl status incus-agent.service
> return an error:
> systemd[1]: incus-agent.service - Incus - agent was skipped because of an
> unmet condition check
> (ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.incus).
The incus-agent service is by design not intended to run on a host
system, but only in a virtual machine (thus the ConditionPathExists
check). Normally the Incus daemon will dynamically inject the agent
into a VM, but it is also possible to generate VM images that install
the agent via its package.
> > I see that the incus package has been removed
> $ dpkg -l | grep incus
> rc incus 6.0.3-2~bpo12+1
> ii incus-agent 6.0.3-4~bpo12+1
> ii incus-client 6.0.3-4~bpo12+1
> ii incus-tools 6.0.3-2~bpo12+1
The Incus package for Debian was refactored to more closely match the
upstream packaging provided by Zabbly. There's a NEWS entry about
this[1], and from the above package list I can see that the "incus-
base" package wasn't installed. This was because of the qemu dependency
(below), but that's the root cause of why Incus wasn't starting for
you. (Also note the different package versions: -2~bpo12+1 vs -
4~bpo12+1.)
> So I tryied to insall incus
> # apt install incus
> [...]
> The following packages have unmeet dependency: <- note I try to
> translate from italian.
> incus : Depend: qemu-system-x86 (>= 1:8.0) but version 1:7.2+dfsg-7+deb12u12
>has been installing
>
> So I added the backport repo in /etc/apt/sources.list adding the
> following:
> deb https://deb.debian.org/debian bookworm-backports main non-free
contrib non-free-firmware
>
> and then installing the incus package
> # apt install -t bookworm-backports incus incus-extra
Yes, the minimum required version of qemu was bumped. It's available
in bookworm-backports, but apt has to be hinted to install it to
properly resolve the dependencies of the incus package. Note that it's
typically unnecessary to install the incus-extra package, unless you
need some of the tools it provides.
With the packaging changes, if you don't need to run VMs in Incus,
you can safely remove the incus package and its qemu dependencies;
everything needed to run containers is part of the incus-base package.
Lastly, a friendly reminder that for backported packages the BTS
isn't the best place to report bugs[2]. Please send bug reports to the
[email protected] list instead.
Mathias
[1] --
https://salsa.debian.org/go-team/packages/incus/-/blob/debian/sid/debian/NEWS?ref_type=heads
[2] -- https://backports.debian.org/Instructions/#index6h2
signature.asc
Description: This is a digitally signed message part
--- End Message ---
