Insecure Container Registry Configuration
Overview
Using insecure Docker registries (HTTP rather than HTTPS, or self-signed certificates without verification) exposes:
- Image pull/push credentials to network interception
- Registry poisoning through MITM — serving malicious images
Remediation
- Use HTTPS for all container registries
- Configure proper TLS certificates
- Use
--insecure-registryonly in development, never in production