canal fails to start due to quay.io not being present in the set of valid registries

[mcastelino]

crio has started enforcing registry origin checks. Hence all registries used by the stack need to be on the whitelist. We should update /etc/containers/registries.conf or replace it with all valid registries.

/etc/containers/registries.conf

# This is a system-wide configuration file used to
# keep track of registries for various container backends.
# It adheres to TOML format and does not support recursive
# lists of registries.

# The default location for this configuration file is /etc/containers/registries.conf.

# The only valid categories are: 'registries.search', 'registries.insecure',
# and 'registries.block'.

[registries.search]
registries = ['docker.io', 'quay.io']

# If you need to access insecure registries, add the registry's fully-qualified name.
# An insecure registry is one that does not have a valid SSL certificate or only does HTTP.
[registries.insecure]
registries = ['docker.io', 'quay.io']


# If you need to block pull access from a registry, uncomment the section below
# and add the registries fully-qualified name.
#
# Docker only
[registries.block]
registries = []

[mcastelino]

/cc @grahamwhaley @ganeshmaharaj

[krsna1729]

@mcastelino we should not update insecure registries

[mcastelino]

The root cause for due to

#70

This is not a registry issue.