How to push to an http insecure registry

[alexpdp7]

Hi,

I'm making some experiments with docker.io/paketobuildpacks/builder-jammy-full, trying to build an image as a Kubernetes job and push to an insecure registry internal to the cluster. I have found that the creator defaults to https:

Error checking read access: Get "https://registry:5000/v2/": http: server gave HTTP response to HTTPS client

, and I cannot find a place to specify http. Is there any way to do this? I'm just trying to do in-cluster builds, which won't be exposed outside a trusted environment.

Thanks,

Álex

[alexpdp7]

I added a self-signed certificate for my registry, but reviewing both the Paketo docs and the CNB docs, I see references to adding CA certs, but no actual way to add them to the builder.

I'd rather use HTTP, because HTTPS is not necessary on my environment- but if HTTP is impossible, I can use HTTPS. I might try to inject them in the builder's /etc/ssl/ or whatever, but it seems an undocumented hack.

[alexpdp7]

Stumbled into buildpacks/spec#364 today.