[Request]: Add ability to add insecure registry for pull/push images
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### Feature or enhancement request details
A lot of times for development you need to use other platforms in combination.
Right now, I am trying to play with apple/container and crc (local openshift), that has its own registry built in.
With docker I can just do
```
docker login -u kubeadmin -p $(oc whoami -t) default-route-openshift-image-registry.apps-crc.testing
```
But container fails, as the certificate is self signed.
Sure, I can probably export the certificate and install it, but at the same time I don't want to do it for every crc instance, and I don't want to install self signed CA certificate in the keychain to compromise my macOS. The best option would be for me just trust this route container push to crc registry.
I would expect a configuration or a flag to add insecure registries to `container`, like `default-route-openshift-image-registry.apps-crc.testing` so the certificate verification will be completely ignored.
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Assessment
This issue has not been assessed yet.