Bug 1812505

Summary:	docker won't start because registries service won't start
Product:	Red Hat Enterprise Linux 7	Reporter:	Ed Santiago <santiago>
Component:	skopeo	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	7.8	CC:	ddarrah, dornelas, jnovy, lsm5, tsweeney, yujiang
Target Milestone:	rc	Keywords:	Extras, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	skopeo-0.1.40-7.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-01 00:26:02 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:	1744505, 1810052

Description Ed Santiago 2020-03-11 13:07:32 UTC

Docker service doesn't start: dependency error. 


   Mar 11 08:43:24 esm-rhel78-1 systemd[1]: Dependency failed for Docker Application Container Engine.
   -- Subject: Unit docker.service has failed
   -- Defined-By: systemd
   -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
   --
   -- Unit docker.service has failed.
   --
   -- The result is dependency.
   Mar 11 08:43:24 esm-rhel78-1 systemd[1]: Job docker.service/start failed with result 'dependency'.
   Mar 11 08:43:24 esm-rhel78-1 systemd[1]: Unit registries.service entered failed state.
   Mar 11 08:43:24 esm-rhel78-1 systemd[1]: registries.service failed.

The error message from registries.service is completely useless:

   Mar 11 08:45:38 esm-rhel78-1 registries[15440]: Unable to load and parse /etc/containers/registries.conf

Root cause: fancy-quotes in 'docker.io' in /etc/containers/registries.conf (i.e. microsoft-word-editor quotes instead of ASCII single quote)

containers-common-0.1.40-8.el7_8.x86_64

Comment 12 errata-xmlrpc 2020-04-01 00:26:02 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1230