Closed stoeps13 closed 1 year ago
Hi @stoeps13, a change has been pushed to make insecure-registries
configurable.
With Harbor, Docker is not needed to deploy the Component Pack so it's not a supported use case of this repo, but this change should provide flexibility to address the issue described.
PR #225 now allows configurable insecure-registries
The setup creates the entry for
"insecure-registries": ["{{ docker_registry_url }}"],
, but then the docker service is not starting.Error message:
This should be replaced with
"insecure-registries": ["{{ docker_registry_url.split('/')[0] }}"],
that just the hostname is set to insecure-registries. Then docker service can be started.On the other side, I want to discuss this setting when you deploy from harbor. When we put hclcr.io to insecure registries, even when it uses a valid certificate, then you're vulnerable for man in the middle attacks, because the docker daemon does not recognize that the attacker provides a self registered certificate.