sdk_container/containerd: Add registry config_path #3045
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sdk_container/containerd: Add registry config_path
Update containerd config to include the crio registry plugin that defines the config_path. This allows users to add host specific configuration for containerd without having to overwrite the default containerd config.
How to use
This config allows users to easily drop in hosts file under
etc/containerd/certs.d
as explained here, in order to configure registry specific configs (mirrors, header, skip_tls, ... )Testing done
have to use the service override mechanism to change the default config file of containerd. Copied the containerd config of the MR into /etc/containerd/config.toml. Restarted containerd and after that:
if the /etc/containerd/certs.d directory does not exist or is empty, containerd does NOT have any issues
I was then able to add hosts files based on the examples above and create mirrors
Changelog entries added in the respective
changelog/
directory (user-facing change, bug fix, security fix, update)Inspected CI output for image differences:
/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.Resolves: flatcar/Flatcar#583