RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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 '{}'

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.

docker-latest is EOL. Closing...