Hi,

Debian CI is switching away from lxc containers in favor of incus Containers.
This is motivated by security concerns from us; incus is based on lxc, but
orchestrates containers substantially different: containers are not privileged
(so root in the container is not uid 0 outside of it), and incus imposes a
stricter isolation from the host system).

suricata passes its tests under lxc, but fails under incus.
The relevant part of the failure is (hopefully):
The full autokpgtest logs are available at:
https://ci.debian.net/experiments/8/regressions/
(please beware of pagination)

Common types of failure and suggested fixes are being documented at:
https://wiki.debian.org/ContinuousIntegration/LxcToIncus

Note that for the time being, suricata is still being tested under lxc to
avoid disturbing its testing migration test results.

If you decide to add the `isolation-machine` restriction to get this package
tested under qemu, please mention that explicitly when closing this bug (it's
fine to do that only in the package changelog entry that closes the bug) so
that we can configure your package for qemu on ci.debian.net.

Hello,

this bug is now fixed in the Salsa git repository [1] and will be part
of the next upload on the next Suricata upstream release.

The release is scheduled upstream for 2026-09-15.
If this adds too much delay to your incus migration, please let me know
and I will do an earlier upload.

Thanks for reporting.

Regards,
Andreas

[1]
https://salsa.debian.org/pkg-suricata-team/pkg-suricata/-/commit/f07e0985187a5442a443d54792a0dc51e6e543f1