Replies: 1 comment 5 replies
-
|
Hey @flixman We have the same status as you, our CI is pushing the images always to dockerhub, and the local env is pulling it from our registry which is proxy-mirror to dockerhub. it is working well. |
Beta Was this translation helpful? Give feedback.
-
|
@amir-bialek But this is a bit weird: Should I switch from proxy mode to normal mode, than I can push the images to it. After that I switch it back to mirror and I can pull those images, meaning: considering the fact that I am getting a 500 error from the mirror, this seems more a use case that was not considered (and that guards were not put in to prevented) rather than intended behavior. What would be the "solution" then? To have a private registry and the mirror, thus duplicating the space for the repo? That is not nice, neither :-/ |
Beta Was this translation helpful? Give feedback.
-
It's not weird. No. You don't push things into caching proxies: the cache is populated by pulling things out of the store. This is pretty much the standard behaviour of any caching proxies, not just registry cache proxy. |
Beta Was this translation helpful? Give feedback.
-
|
but this is not entirely a "caching proxy", right? On a caching proxy I'd be able to push and pull, meaning that the proxy becomes a local mirror of the remote store. In this case, this is is advertised as a "pull through cache"... without specifying what will happen to the pushes. If I am running a local register, to which I push and pull images, and I read about the "pull through cache" feature, anybody will read it as a feature extending the existent configuration (as opposed to replacing it, which is what actually happens). |
Beta Was this translation helpful? Give feedback.
-
|
I am not sure about the exact definition, but for us it is working well. |
Beta Was this translation helpful? Give feedback.
-
Honestly, I don't know what you're talking about here. It literally is a caching proxy: it caches container images. Take Cloudflare caching for example: you smack a GET to some content and CF can cache it, but it will never cache POST/PUT data. I honestly don't know of any caching proxy to which you can "push data". |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a private registry to which I can push/pull containers successfully. As I want to reduce the queries/traffic to docker hub while doing development, yesterday I enabled the proxy feature through the container environment variable
REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io. This works as expected for the pulls (both the images available locally on the registry and in docker.io can be pulled, with the latter ones being cached by the registry), but I have lost all possibility to push to my registry (I am getting a 500 Internal Server Error, and on the registry logs I am getting a 401 message with the description "denied: requested access to the resource is denied").Is this expected behavior?
Beta Was this translation helpful? Give feedback.
All reactions