Before you open an issue, you should search for similar issues.
Especially for issues that deal with starting the docker-registry-frontend we have seen a tremendous amount
of issues and most of the time a reference to the example-setup
folder was enough for the issue reporter to solve the issue on her own.
Please, make sure to provide all the information asked for below and then delete everything above Expected behavior including this line.
Expected behavior
[x] Please describe what you tried to do and what you expect the software to act like.
Actual behavior
[x] Please describe what happened instead of the expected behavior.
Steps to reproduce the problem
[x] Please describe how a developer can reproduce the issue that you faced.
Make sure you include information how you configured or started the registry and the frontend.
Specifications
[x] Which version of docker (docker version) are you running?
[x] Which operating system do you use?
[x] Which version of the docker-registry-frontend are you running?
If you have the frontend running already you can find the version at the very bottom on every page.
Otherwise you can provide the output of docker images | grep "docker-registry-frontend".
Before you open an issue, you should search for similar issues. Especially for issues that deal with starting the docker-registry-frontend we have seen a tremendous amount of issues and most of the time a reference to the example-setup folder was enough for the issue reporter to solve the issue on her own.
Please, make sure to provide all the information asked for below and then delete everything above Expected behavior including this line.
Expected behavior
Actual behavior
Steps to reproduce the problem
Specifications
docker version) are you running?docker images | grep "docker-registry-frontend".