Bug 1288104 - machinectl start won't launch container from image
Summary: machinectl start won't launch container from image
Status: CLOSED DUPLICATE of bug 1266776
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
(Show other bugs)
Version: 23
Hardware: Unspecified Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 14:29 UTC by Neil Wilson
Modified: 2015-12-03 15:17 UTC (History)
6 users (show)

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.