RPJosh
/
docker-registry-proxy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

0.4.1 release, since I borked 0.4.0

pull/56/head 0.4.1
Ricardo Pardini 2020-10-08 17:34:41 +02:00
parent d57a8ce4f5
commit 3c10258e6d
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -16,7 +16,7 @@ for this to work it requires inserting a root CA certificate into system trusted
## master/:latest is unstable/beta ## master/:latest is unstable/beta
- `:latest` and `:latest-debug` Docker tag is unstable, built from master, and amd64-only - `:latest` and `:latest-debug` Docker tag is unstable, built from master, and amd64-only
- Production/stable is `0.4.0`, see [0.4.0 tag on Github](https://github.com/rpardini/docker-registry-proxy/tree/0.4.0) - this image is multi-arch amd64/arm64 - Production/stable is `0.4.1`, see [0.4.1 tag on Github](https://github.com/rpardini/docker-registry-proxy/tree/0.4.1) - this image is multi-arch amd64/arm64
- The previous version is `0.3.0`, see [0.3.0 tag on Github](https://github.com/rpardini/docker-registry-proxy/tree/0.3.0) (amd64 only) - The previous version is `0.3.0`, see [0.3.0 tag on Github](https://github.com/rpardini/docker-registry-proxy/tree/0.3.0) (amd64 only)
## Usage ## Usage
@ -38,7 +38,7 @@ docker run --rm --name docker_registry_proxy -it \
-p 0.0.0.0:3128:3128 \ -p 0.0.0.0:3128:3128 \
-v $(pwd)/docker_mirror_cache:/docker_mirror_cache \ -v $(pwd)/docker_mirror_cache:/docker_mirror_cache \
-v $(pwd)/docker_mirror_certs:/ca \ -v $(pwd)/docker_mirror_certs:/ca \
rpardini/docker-registry-proxy:0.4.0 rpardini/docker-registry-proxy:0.4.1
``` ```
### DockerHub auth ### DockerHub auth
@ -54,7 +54,7 @@ docker run --rm --name docker_registry_proxy -it \
-v $(pwd)/docker_mirror_certs:/ca \ -v $(pwd)/docker_mirror_certs:/ca \
-e REGISTRIES="k8s.gcr.io gcr.io quay.io your.own.registry another.public.registry" \ -e REGISTRIES="k8s.gcr.io gcr.io quay.io your.own.registry another.public.registry" \
-e AUTH_REGISTRIES="auth.docker.io:dockerhub_username:dockerhub_password your.own.registry:username:password" \ -e AUTH_REGISTRIES="auth.docker.io:dockerhub_username:dockerhub_password your.own.registry:username:password" \
rpardini/docker-registry-proxy:0.4.0 rpardini/docker-registry-proxy:0.4.1
``` ```
### Simple registries auth (HTTP Basic auth) ### Simple registries auth (HTTP Basic auth)
@ -82,7 +82,7 @@ docker run --rm --name docker_registry_proxy -it \
-v $(pwd)/docker_mirror_certs:/ca \ -v $(pwd)/docker_mirror_certs:/ca \
-e REGISTRIES="reg.example.com git.example.com" \ -e REGISTRIES="reg.example.com git.example.com" \
-e AUTH_REGISTRIES="git.example.com:USER:PASSWORD" \ -e AUTH_REGISTRIES="git.example.com:USER:PASSWORD" \
rpardini/docker-registry-proxy:0.4.0 rpardini/docker-registry-proxy:0.4.1
``` ```
### Google Container Registry (GCR) auth ### Google Container Registry (GCR) auth
@ -105,7 +105,7 @@ docker run --rm --name docker_registry_proxy -it \
-e AUTH_REGISTRIES_DELIMITER=";;;" \ -e AUTH_REGISTRIES_DELIMITER=";;;" \
-e AUTH_REGISTRY_DELIMITER=":::" \ -e AUTH_REGISTRY_DELIMITER=":::" \
-e AUTH_REGISTRIES="gcr.io:::_json_key:::$(cat servicekey.json);;;auth.docker.io:::dockerhub_username:::dockerhub_password" \ -e AUTH_REGISTRIES="gcr.io:::_json_key:::$(cat servicekey.json);;;auth.docker.io:::dockerhub_username:::dockerhub_password" \
rpardini/docker-registry-proxy:0.4.0 rpardini/docker-registry-proxy:0.4.1
``` ```
## Configuring the Docker clients / Kubernetes nodes ## Configuring the Docker clients / Kubernetes nodes
@ -155,7 +155,7 @@ Test your own registry caching and authentication the same way; you don't need `
## Developing/Debugging ## Developing/Debugging
Since `0.4.0` there is a separate `-debug` version of the image, which includes `nginx-debug`, and has `mitmproxy` (actually `mitmweb`) inserted after the CONNECT proxy but before the caching logic. Since `0.4.1` there is a separate `-debug` version of the image, which includes `nginx-debug`, and has `mitmproxy` (actually `mitmweb`) inserted after the CONNECT proxy but before the caching logic.
This allows very in-depth debugging, but tends to be unstable with huge layers. Use sparingly, and definitely not in production. This allows very in-depth debugging, but tends to be unstable with huge layers. Use sparingly, and definitely not in production.
```bash ```bash
@ -164,7 +164,7 @@ docker run --rm --name docker_registry_proxy -it
-p 0.0.0.0:3128:3128 \ -p 0.0.0.0:3128:3128 \
-v $(pwd)/docker_mirror_cache:/docker_mirror_cache \ -v $(pwd)/docker_mirror_cache:/docker_mirror_cache \
-v $(pwd)/docker_mirror_certs:/ca \ -v $(pwd)/docker_mirror_certs:/ca \
rpardini/docker-registry-proxy:0.4.0-debug rpardini/docker-registry-proxy:0.4.1-debug
``` ```
- `DEBUG=true` enables the mitmweb proxy, accessible on port 8081 - `DEBUG=true` enables the mitmweb proxy, accessible on port 8081