Add docker-compose example about docker-registry-proxy

I am hoping this doesn't reopen the "issue" but I wanted to put a note here in case someone else has a similar problem.

The problem was not with the application, it was with docker-compose. When I use the same configuration as you (Mac + 1.27.4) it works just fine (Thanks for that by the way - I love the idea of not relying on Docker Hub). However the bug I was experiencing is manifested when using Ubuntu 20.04 + 1.25.0.

So the moral to the story is: I need to figure out why Ubuntu hasn't updated my docker components since November of last year.

[rpardini]

There you go, added and fixed your compose in https://github.com/rpardini/docker-registry-proxy/tree/master/docs/compose

Different error this time

Steps to recreate

$ git clone https://github.com/rpardini/docker-registry-proxy.git
$ cd docker-regisry-proxy/docs/compose

(modify secrets.env to set username and password)

$ docker-compose up

Results

$ docker-compose up 
Creating network "compose_default" with the default driver
Creating compose_docker_registry_proxy_1 ... done
Attaching to compose_docker_registry_proxy_1
docker_registry_proxy_1  | Adding certificate for registry: docker.caching.proxy.internal
docker_registry_proxy_1  | Adding certificate for registry: registry-1.docker.io
docker_registry_proxy_1  | Adding certificate for registry: auth.docker.io
docker_registry_proxy_1  | xargs: unmatched double quote
compose_docker_registry_proxy_1 exited with code 1

Let me know if there is anything I can do to help troubleshoot.

[rpardini]

Sorry man, it works for me, on Mac/Linux + Docker-compose 1.27.4 and others. (with no secrets change)
This proxy does no validation of the environment vars, and uses them directly in bash code; make sure your edits are valid.

[rLoka]

Had the same issue. Upgrading docker-compose to the latest version solved the issue!