Bug 1288104

Summary:	machinectl start won't launch container from image
Product:	[Fedora] Fedora	Reporter:	Neil Wilson <neil>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	johannbg, lnykryn, msekleta, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-03 15:17:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Neil Wilson 2015-12-03 14:29:48 UTC

Description of problem:

The systemd-nspawn@ unit file has an overly restrictive device list and fails when it tries to launch an image in the machinectl image list. 


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

Name        : systemd
Arch        : x86_64
Epoch       : 0
Version     : 222
Release     : 8.fc23

How reproducible:

Essentially this: https://github.com/systemd/systemd/issues/1446

Comment 1 Neil Wilson 2015-12-03 15:17:37 UTC


*** This bug has been marked as a duplicate of bug 1266776 ***