Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Publish a Docker image from Gitlab pipeline using Kaniko to Proget
-
Hello,
I'm trying to publish a Docker image from Gitlab pipeline using Kaniko to Proget.
With HTTP, everything goes smoothly, but with HTTPS, an error occurs: stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peer
I checked all certificates, and they are valid.
Do you have any advice on continuing the troubleshooting?
The full error:
Pushing image to xxx.lokal:8625/dev-images/image-name:latest
error pushing image: failed to push to destination xxx.lokal:8625/dev-images/image-name:latest: Head "https://xxx.lokal:8625/v2/dev-images/image-name/blobs/sha256:944cb9daf72b35ac4c2a49b5ad6d66fd45e201e5fd2a67b47cb5d4b4c838f19e": stream error: stream ID 47; HTTP_1_1_REQUIRED; received from peerBest Regards,
Pedro
-
Hi @pmsensi,
I'm sorry I'm not sure. The error
HTTP_1_1_REQUIRED
indicates that an intermediary (e.g., proxy or load balancer) is rejecting HTTP/2 requests and requiring HTTP/1.1.So, I would check with the proxies or load balancers between Kaniko (running in your GitLab pipeline) and ProGet. I suspect it's interfering with HTTP/2 traffic, causing the server to fall back to HTTP/1.1.
Alternatively, you can try forcing Kaniko to use HTTP/1.1 instead of HTTP/2. I don't know how to do that, but there may be an
--insecure
flag that may also work.Thanks,
Alana
-
Hello @atripp ,
Thank you for your help.
We have an intermediate certificate (proxy), which I think, as you point out, can be the problem. I will clarify with our IT department. Anyway, after reading a little bit more, there is a variable to force Kaniko to use HTTP/1.1.
variables: GODEBUG: "http2client=0"
After adding that, everything works :)
Thank you!
Best Regards,
Pedro