-
Notifications
You must be signed in to change notification settings - Fork 616
Description
vendor.ef9e0e04.js:5 GET http://pd-dockerrepo-as1.dfci.harvard.edu:8080/v1/search?q= 502 (Proxy Error)
(anonymous) @ vendor.ef9e0e04.js:5
v @ vendor.ef9e0e04.js:5
j @ vendor.ef9e0e04.js:4
i @ vendor.ef9e0e04.js:5
(anonymous) @ vendor.ef9e0e04.js:5
$eval @ vendor.ef9e0e04.js:5
$digest @ vendor.ef9e0e04.js:5
$apply @ vendor.ef9e0e04.js:5
(anonymous) @ vendor.ef9e0e04.js:5
dispatch @ vendor.ef9e0e04.js:2
q.handle @ vendor.ef9e0e04.js:2
Navigated to https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fkwk%2Fdocker-registry-frontend%2Fissues%2Fnew
login:1 Unchecked runtime.lastError: The message port closed before a response was received.
Navigated to https://github.com/kwk/docker-registry-frontend/issues/new
new:1 Unchecked runtime.lastError: The message port closed before a response was received.
Expected behavior
- Please describe what you tried to do and what you expect the software to act like.
Actual behavior
- Please describe what happened instead of the expected behavior.
Steps to reproduce the problem
- 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
- Which version of docker (
docker version) are you running? - Which operating system do you use?
- 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".