Testing locally?

[leedtan]

Can I develop with this locally before hosting it on a live remote proxy server? Is there a doc (I can't find one) on how to test this locally? When I run locally my docker image builds but I get error message:

are not shared from OS X and are not known to Docker.

When I reduce the docker build command to only specify the following, the docker image runs:

docker run -d --name docker-registry-proxy --net=host \
  -v /tmp/dockerdbg/cache:/cache \
  -e PORT=5000 \
  -e RESOLVER=8.8.8.8 \
  -e UPSTREAM=https://<AWS address>.amazonaws.com \
  -e AWS_ACCESS_KEY_ID=<my access key> \
  -e AWS_SECRET_ACCESS_KEY<my secret access key> \
  -e AWS_REGION=us-east-1 \
  -e ENABLE_SSL=false \
  esailors/aws-ecr-http-proxy:latest

But I dont get a response when I try to query.

For IPV4 I make the most promising results:
->docker pull <my IPV4>:5000/<my model name>:<tag>
->Error response from daemon: Get https://<my IPV4>:5000/v2/: Service Unavailable

[matlockx]

When you are on a Mac you would need to configure docker to use other mount points as well if you do not use the default ones like /tmp. So in our example from the readme it's /registry which is not part of the mount list on a Mac. Either you set it in the settings of docker or you change that to /tmp/registry for example. There should not be much needed in addition to that for testing it locally with the example from the readme. Does that help?

[leedtan]

Thanks. I think I actually got that working, but then realized that this system runs docker login on launch and relies on that connection to proxy requests.
What I was trying to do was to manage multiple user logins with access to their own respective repositories dynamically created over time as new we get new users and they create new repositories that we proxy and use ecr repositories behind our proxy.
Do you think this system works for that use case? I couldn't figure out how to make that tweak from this base system.