-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buildkit and Harbor Proxy Cache #1787
Comments
I'm not sure why the above mentioned similar issue and moby/moby#40262 are closed while they show a disparity in functionality between buildkit and the "normal" builder. |
Buildkit v0.6 (vendored in 19.03) / Containerd 1.2 do not support mirrors that don't actually contain the data and return error (instead of forward to upstream in that case). Newer version support it. This is a possible explanation. I have no visibility what Harbor Proxy Cache actually does. |
I hope the underlying issue is the same as with the OP, but with version 19.03.13, containerd 1.3.7; I still see this behaviour:
If you think this is a different issue, I'll gladly open a new issue. |
It is the vendored containerd library version that matters so 19.03 is always affected. Try with 20.10-beta or newer buildkit with |
@tonistiigi Thanks a lot; this works! But it seems I hijacked the thread then, sorry. |
Due to hub docker rate limit policy
I had to install harbor 2.1 and arranged its a proxy cache.
It is working as expected such as if I use it in my deployment.yaml files or directly pull from harbor cache there is no problem.
Docker pull has no problem.
docker pull harbor-cache.abc.com/docker/library/centos:7
but when I try to build an image from Dockerfile I got below error.
There is no error for the below dockerfile
Any suggestion?
Looks like a similar issue
The text was updated successfully, but these errors were encountered: