smoke-tests autopkgtest fails in unprivileged containers

Bug #1979358 reported by Paride Legovini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firejail (Debian)
Fix Released
Unknown
firejail (Ubuntu)
Fix Released
Undecided
Paride Legovini

Bug Description

The smoke-tests autopkgtest fails in containers, but isolation-machine is not declared in d/t/control for the test. This is blocking the package in -proposed as the armhf tests run in a container.

CVE References

Paride Legovini (paride)
tags: added: update-excuse
Changed in firejail (Ubuntu):
status: New → Fix Committed
assignee: nobody → Paride Legovini (paride)
Revision history for this message
Reiner Herrmann (deki) wrote :

Hi Paride,

the smoke-tests don't actually need isolation-machine.
The tests fail because firejail can't create /dev/zero:

> Error: cannot create /dev/zero device: Operation not permitted
> Error: proc 2825 cannot sync with peer: unexpected EOF

I guess the containers are mounted with "nodev" or are otherwise preventing creation of devices.
But the same error would happen if VMs / isolation-machines were configured similarly.

Paride Legovini (paride)
tags: added: block-proposed
Revision history for this message
Paride Legovini (paride) wrote :

Hi Reiner, I'm going to reply to the linked Debian bug so we don't duplicate the discussion.

Changed in firejail (Debian):
status: Unknown → New
Revision history for this message
Paride Legovini (paride) wrote :

I am merging the merge 0.9.70-1 in a PPA, will trigger autopkgtests from there.

Paride Legovini (paride)
summary: - smoke-tests autopkgtest fails in container, but isolation-machine is not
- declared
+ smoke-tests autopkgtest fails in unprivileged containers
Paride Legovini (paride)
tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firejail - 0.9.70-1ubuntu1

---------------
firejail (0.9.70-1ubuntu1) kinetic; urgency=medium

  * Merge with Debian unstable. (LP: #1979358)
    Remaining changes:
    - When running autopkgtests, do not attempt to install firefox on
      architectures where it isn't built any longer (LP #1965314)
      - debian/tests/control

firejail (0.9.70-1) unstable; urgency=medium

  * New upstream release.
    - fix sound playback in chromium (Closes: #1003650)
  * Drop patches applied upstream.
  * Enable new IDS feature during build.
  * Mark nvm.profile as removed.
  * Extend lintian-override match to include profstats.
  * Move profiles tests back from smoke- to simple-tests, as they
    are too environment dependent.
  * Add procps to test dependencies.

firejail (0.9.68-4) unstable; urgency=high

  * Fix local root exploit reachable via --join logic. (CVE-2022-31214)
    (Closes: #1012510)

firejail (0.9.68-3) unstable; urgency=medium

  * Fix hyperrogue profile, which causes autopkgtest failure in Ubuntu CI.

firejail (0.9.68-2) unstable; urgency=medium

  * Add file to test dependencies.

firejail (0.9.68-1) unstable; urgency=medium

  * New upstream release.
  * Remove hostnames conffile, which has been renamed and moved to libdir.
  * Add a superficial autopkgtest that should run stable, but can
    catch breakage.

firejail (0.9.68~rc1-1) experimental; urgency=medium

  * New upstream release candidate.
    - fix telegram-desktop profile (Closes: #1002998)
    - allow webext directory in chromium profile (Closes: #1003234)
    - blacklist rxvt when perl is blacklisted (Closes: #1003259)
    - don't reject empty arguments (LP: #1934698)
  * Rename lintian tag in override: setuid-binary -> elevated-privileges.
  * Add lintian overrides for non-standard-executable-perm and
    executable-in-usr-lib.
  * Install new .config files.
  * Remove conffile: disable-passwdmgr.inc.
  * Document new copyright.
  * Bump Standards-Version to 4.6.0.
  * Bump copyright years to 2022.

 -- Paride Legovini <email address hidden> Wed, 22 Jun 2022 19:53:11 +0200

Changed in firejail (Ubuntu):
status: Fix Committed → Fix Released
Changed in firejail (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.