Using a local container image registry without TLS, the bitbucket workers fail

[Ira Abramov]

TL;DR: I get an error but only when the pipeline runs:

http: server gave HTTP response to HTTPS client


In full: My machine is on prem, I run 3 workers for my CI, the build was working fine while I was working with the docker hub. But once I am basing on a local image and pushing to a local image registry (port 5000, no TLS, default instructions) I get the error during a pipe run.

On the host itself, I have no problem pulling and pushing.
I added "insecure-registries" in /etc/docker/daemon.json just in case.
I even tried mounting /etc/docker in my bitbucket workers.
when I exec a shell in a running BB runner container I can do a ./docker pull regmachine:5000/image:latest and I get no complaints, but when bitbucket runs a build remotely, I get a complaint about port 5000 not answering as https. I suppose I can give it a borrowed cert or a self-signed one, but I feel there must be a quicker solution I am missing.

What have I missed?

[Ben]

Hi Ira,

To investigate this effectively - we will need access to your workspace to check your YML configuration and build logs. We can only do so with a support ticket, however, as our systems require a ticket to be present.

I can see that you are on a paid Standard plan, and thus qualify for support directly with our support team. Please raise a ticket using your paid workspace URL:

• https://support.atlassian.com/contact/

If you're having issues raising a ticket, please let me know which timezone you are in so I can raise one on your behalf with the appropriate team in your area.

Cheers!

- Ben (Bitbucket Cloud Support)