This message was deleted.
# k3d
a
This message was deleted.
w
Hi there! What's the problem with the separately created registry and Tilt?
m
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
w
And when doing it with
--registry-create
, that same thing succeeds? 🤔
m
Strangely, yes.
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 😞
w
But Tilt is outside of the cluster isn't it? So the registries.yaml shouldn't have any influence, right?
m
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>
Identified the root cause of the issue. My registry was setup as a pull-through proxy and it doesn't support push.
156 Views