smoke-tests autopkgtest fails in unprivileged containers
Bug #1979358 reported by
Paride Legovini
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
tags: | added: update-excuse |
Changed in firejail (Ubuntu): | |
status: | New → Fix Committed |
assignee: | nobody → Paride Legovini (paride) |
tags: | added: block-proposed |
Changed in firejail (Debian): | |
status: | Unknown → New |
summary: |
- smoke-tests autopkgtest fails in container, but isolation-machine is not - declared + smoke-tests autopkgtest fails in unprivileged containers |
tags: | removed: block-proposed |
Changed in firejail (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
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.