Description

Using the documented public interface, there is no way to use the "OCI publication" feature with registries using plain HTTP (AKA insecure). Although no productive set-up should be using plain HTTP, it is very common experimenting locally.

I found out in the code that there is a hidden way to activate such a feature: setting the environment variable __TEST__INSECURE__REGISTRY__

It would be good to:

• either have a CLI flag for this feature, like many other tools do
• or document the, IMO not so nice, environment variable __TEST__INSECURE__REGISTRY__ possibility