Replies: 2 comments 3 replies
-
@kikokikok thanks for trying out zot and the feedback. You are likely referring to (as an enhancement): We will take a look at how we can improve this in the short-term. Meanwhile, as a workaround, maybe enable a periodic poll as well? is this viable for you? |
Beta Was this translation helpful? Give feedback.
-
Hello @kikokikok sync on demand works like this:
Actually we do maintain an open connection for the on demand sync, but only for the manifest, when zot finishes syncing it will respond to the manifest call, and from that point all the layers should already be synced. I've tried to reproduce this with a multi stage Dockerfile and it works on my side. I don't understand how your setup tries to pull layers before pulling the manifest. The only thing that comes to my mind is that you get a timeout because zot doesn't actually send anything on the open connection, Can you give us logs from zot and also from docker. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi all,
First I'd like to thank you for this great project which brought amazing value to us.
I'd like though, to share with you a scenario where I feel zot could do a lot better but unfortunately falls a bit short.
In our context, we use zot as a local laptop registry for developers in their local all-batteries included k3s cluster.
Zot is configured as an on-demand proxy to a company-wide shared artifactory instance.
In this particular setup what we expect from zot is the ability for developers to build locally as if the CI was building so that their inner-dev loop is as optimised and fast as possible.
Here is the glitch:
Whenever I have a multi-stage dockerfile to build which is referencing multiple base images through zot but in reality mirrored from the real ones in artifactory, the docker build will fail each time the image layers haven't yet been retrieved and the same applied on pull scenarios from the kubelet of k3s until the image is fully retrieved.
Question: Is it on purpose that we don't maintain an open connection to the caller for any pull until we know if the image exists locally or remotely and only after:
Thanks !
Beta Was this translation helpful? Give feedback.
All reactions