Bug 1260980 - Add possibility to passthrough devices from config
Add possibility to passthrough devices from config
Product: Fedora
Classification: Fedora
Component: mock (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Suchý
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-08 06:50 EDT by David Caro
Modified: 2016-06-26 19:51 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-08 07:52:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Caro 2015-09-08 06:50:06 EDT
Description of problem:
I want to allow the processes inside the chroot to access some of the devices that are available out of the chroot, right now there's no easy way to allow that aside from mounting the whole /dev and setting it as unmanaged (bad idea) or manually populating it yourself.

Having a config option like 'passthrough_devices' where you specify a list of devices would be really helpful.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
One possibility is to create hard links for the devices, but that requires the chroot dev and the system dev to be in the same device (maybe creating a temp dir inside the system /dev and mounting it in the chroot?)
Comment 1 Miroslav Suchý 2015-09-08 07:52:20 EDT
While it is probably doable with current chroot, we are in transition to handle the chroot isolation to systemd-nspawn (can be used with --new-chroot option now). And with systemd-nspawn the passthrough of devices is not possible. See:
Comment 2 David Caro 2015-09-08 08:02:42 EDT
Thanks for the update :/

We are intensively and extensively using mock for our projects, that change to systemd-nspawn might break some things, what is the roadmap?

Note You need to log in before you can comment on or make changes to this bug.