Cian Butler

So we started encoding, we said, oh, this is encoding Trio 7s as, it's saying these Trio 7s have a content length of 200 megabytes or whatever the eventual image size is going to be.

Let's not do that.

That's what's breaking this.

Let's respond with actual valid HTTP and say the content length is zero.

So we did that, and Docker freaked out.

It started... Well, actually, we ran tests, and they were working.

We were like, great, our end-to-end tests are still working in this.

This is fine.

And then one of our developers came in and said, hey, I can't get my local dev to start.

So we started debugging it.

And it turned out that their local dev was getting the wrong metadata.

And my local dev was working completely fine.

And that's where it became really weird.

I was using BuildX and they were not using BuildX for building their Docker images and running their Docker images.

And that's when we realized it was very specific clients were doing stuff differently.

Some of them were checking the metadata from the header and some of them were doing the maths themselves and putting it in there.

We rolled back the change of the header.

We then moved, we then, and we moved the logic around.

We moved the validation of the content length out to the edge network.

So we could do some like after our load balancers had done all their work and hyper had changed.