Bug 1471210

Summary: Cannot enable signature verification for docker-latest
Product: Red Hat Enterprise Linux 7 Reporter: Aaron Weitekamp <aweiteka>
Component: docker-latestAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED EOL QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: amurdaca, dwalsh, imcleod, jhonce, rcyriac, sdodson
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-10 12:46:13 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 Aaron Weitekamp 2017-07-14 17:19:28 UTC
Description of problem:
When enabling signature verification to docker-latest via /etc/sysconfig/docker-latest, service cannot start.

Version-Release number of selected component (if applicable):
$ cat /etc/redhat-release
Red Hat Enterprise Linux Atomic Host release 7.3
$ rpm -q docker-latest
docker-latest-1.13.1-13.gitb303bf6.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. add '--signature-verification=true' to OPTIONS in /etc/sysconfig/docker-latest
2. restart docker-latest

Actual results:
unable to configure the Docker daemon with file /etc/docker-latest/daemon.json: the following directives are specified both as a flag and in the configuration file: signature-verification: (from flag: true, from file: false)

Expected results:
docker-latest restart

Additional info:

Workaround:
1. Edit /etc/docker-latest/daemon.json 'signature-verification": true'
2. remove --signature-verification=true from /etc/sysconfig/docker-latest
3. restart docker-latest

NOTE: /etc/docker/daemon.json content is simply '{}'

Comment 2 Lokesh Mandvekar 2017-07-14 17:50:55 UTC
For docker-latest, the workaround mentioned would be the preferred way to do this. We're avoiding adding options to /etc/sysconfig/docker-latest in favor or /etc/docker-latest/daemon.json

RE: /etc/docker/daemon.json, Scott mentioned we need to ensure a smooth transition from /etc/sysconfig/docker to /etc/docker/daemon.json, however adding options in both places is not allowed so far.

Comment 3 Lokesh Mandvekar 2019-04-10 12:46:13 UTC
docker-latest is EOL. Closing...