Bug 1144206

Summary: [PATCH] Support /etc/sysconfig/docker-storage
Product: Red Hat Enterprise Linux 7 Reporter: Colin Walters <walters>
Component: dockerAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1Keywords: Extras
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1145659 (view as bug list) Environment:
Last Closed: 2016-01-07 21:42:17 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:
Bug Depends On:    
Bug Blocks: 1145659    
Attachments:
Description Flags
[PATCH] Support /etc/sysconfig/docker-storage none

Description Colin Walters 2014-09-19 02:11:31 UTC 
Created attachment 939077 [details]
[PATCH] Support /etc/sysconfig/docker-storage

This will allow installation programs to pre-configure storage easily.
It will be used by Atomic to set up Docker for direct LVM.
---
 docker-storage.sysconfig | 14 ++++++++++++++
 docker.service           |  3 ++-
 docker.spec              |  5 ++++-
 3 files changed, 20 insertions(+), 2 deletions(-)
 create mode 100644 docker-storage.sysconfig
Comment 2 Colin Walters 2014-09-19 19:19:18 UTC 
The rationale for a separate sysconfig file is that in-place modification of /etc/sysconfig/docker is ugly for Anaconda or the disk image generation scripts to do; we'd have to sed.  That's still possible though, it just feels cleaner to me if we separate what admins edit and what tools generate.

Other options are:

1) Have Docker search for an lvm volumes named docker-data, docker-metadata on startup and automatically use them
2) Something else?
Comment 3 Daniel Walsh 2014-09-19 20:36:34 UTC 
Applied to  docker-1.2.0-17.el7

We need to get this into Centos and Fedora.