Unable to add a luet repo from an insecure / http development registry - have evidence of pull from development registry working without Luet

Luet version: luet version 0.34.0-g4c788ccbd18e287c15c9610594daa533b53ffdad 2024-03-15 08:27:52 UTC

CPU architecture, OS, and Version: Linux buildkitsandbox 5.14.21-150500.55.28-default #1 SMP PREEMPT_DYNAMIC Fri Sep 22 10:04:29 UTC 2023 (c11336f) x86_64 x86_64 x86_64 GNU/Linux

Describe the bug

I have a development registry which is insecure and uses HTTP. I have uploaded my Luet repo to this registry. I have already confirmed that the Luet repo is valid, because I have also uploaded it to a secure HTTPS registry, and had no issues accessing it via the luet command:

When attempting to run 'luet repo add' command to add the Luet repo from my insecure and HTTP development registry, I am facing 'server gave HTTP response to HTTPS client' error message.

Regarding my environment - I am using Luet inside of a BuildKit container, and the buildkitd.toml configuration file has my insecure/HTTP development registry configured with 'http' and 'insecure' settings. I know that the buildkitd.toml configuration is working, because I am able to pull images from the same insecure/HTTP development registry using methods other than Luet, such as using 'FROM' in an Earthfile:

To Reproduce

1. Spin up a buildkit container with Luet installed
2. Configure buildkitd.toml configuration file with an insecure/http development registry, for example:

[registry."(registry IP here):80"]
http = true
insecure = true

3. Attempt to run 'luet repo add' to add the insecure/http development registry

Expected behavior

Expected that Luet would be able to use the buildkitd.toml configuration and be able to pull images from the insecure/http registry like other methods of pulling images are able to do.

Logs

Screenshots of logs shown above in the 'Describe the bug' section

Additional context