# If true, pulling images with matching names is forbidden.
# If true, unencrypted HTTP as well as TLS connections with untrusted # If the prefix field is missing, it defaults to be the same as the "location" field. # (taking into account namespace/repo/tag/digest separators) is used. # (only) the TOML table with the longest match for the input image name # The "prefix" field is used to choose the relevant ] TOML table # An array of host registries to try when pulling an unqualified image, in order. # of these registries, it should be added at the end of the list. # spoofed, squatted or otherwise made insecure. # trusted (i.e., registries which don't allow unknown or anonymous users to We recommend only adding registries which are completely
#Ubuntu download for mac code#
# would accidentally pull and run the attacker's image and code rather than the # different `foobar` image at a registry earlier in the search list. # is not first in the search list, an attacker could place a # `foobar` from a registry and expects it to come from. For example, a user wants to pull an image named # When using short names, there is always an inherent risk that the image being # further eliminates the ambiguity of tags. # server (full dns name), namespace, image name, and tag # We recommend always using fully qualified image names including the registry # NOTE: RISK OF USING UNQUALIFIED IMAGE NAMES # For more information on this configuration file, see nf(5).