This message was deleted Rancher Users #k3d

Join Slack

This message was deleted.

# k3d

adamant-kite-43734

12/19/2022, 4:38 AM

This message was deleted.

wide-garage-9465

12/19/2022, 7:10 AM

Hi there! What's the problem with the separately created registry and Tilt?

millions-sunset-36049

12/19/2022, 2:33 PM

With a separate k3d managed local registry, Tilt is unable to push a

docker_build

image to that registry. It is stuck at:

Copy code

STEP 2/3 — Pushing localhost:53419/web:tilt-249c7722da12698c
  Pushing with Docker client
  Authenticating to image repo: localhost:53419
  Sending image data
  0d899785e82a: Retrying in 1 seconds 
  f335579cab20: Retrying in 1 seconds 

Build Failed: docker push: pushing image "localhost:53419/web": unsupported

wide-garage-9465

12/19/2022, 2:52 PM

And when doing it with

--registry-create

, that same thing succeeds? 🤔

millions-sunset-36049

12/19/2022, 2:52 PM

Strangely, yes.

millions-sunset-36049

12/19/2022, 2:53 PM

I even tried to copy the

registry.yml

that k3d generates, align it to the k3d registry that I created and use it but unfortunately it throws the same error again 😞

wide-garage-9465

12/19/2022, 8:59 PM

But Tilt is outside of the cluster isn't it? So the registries.yaml shouldn't have any influence, right?

millions-sunset-36049

12/19/2022, 9:05 PM

Yeah, Tilt auto detects the local registry from the cluster. What I meant about using

registry.yml

was adding the additional mirrors. For example:

Copy code

mirrors:
  "localhost:53419":
    endpoint:
      - <http://k3d-mylocal-registry.localhost:5000>
  "mylocal-registry.localhost":
    endpoint:
      - <http://k3d-mylocal-registry.localhost:5000>
  "mylocal-registry.localhost:5000":
    endpoint:
      - <http://k3d-mylocal-registry.localhost:5000>

millions-sunset-36049

12/20/2022, 9:04 PM

Identified the root cause of the issue. My registry was setup as a pull-through proxy and it doesn't support push.

161 Views

Open in Slack

Previous Next