You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
### TL,DR
4
4
5
-
A caching proxy for Docker; allows centralized management of registries and their authentication; caches images from *any* registry.
5
+
A caching proxy for Docker; allows centralised management of registries and their authentication; caches images from *any* registry.
6
6
7
7
### What?
8
8
@@ -24,13 +24,13 @@ for this to work it requires inserting a root CA certificate into system trusted
24
24
- Env `AUTH_REGISTRIES`: space separated list of `registry:username:password` authentication info. Registry hosts here should be listed in the above ENV as well.
25
25
26
26
```bash
27
-
docker run --rm --name docker_caching_proxy -it \
27
+
docker run --rm --name docker_registry_proxy -it \
@@ -81,6 +81,8 @@ Test your own registry caching and authentication the same way; you don't need `
81
81
82
82
- If you authenticate to a private registry and pull through the proxy, those images will be served to any client that can reach the proxy, even without authentication. *beware*
83
83
- Repeat, this will make your private images very public if you're not careful.
84
+
-**Currently you cannot push images while using the proxy** which is a shame. PRs welcome.
85
+
- Setting this on Linux is relatively easy. On Mac and Windows the CA-certificate part will be very different but should work in principle.
84
86
85
87
#### Why not use Docker's own registry, which has a mirror feature?
0 commit comments