We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I met a phenomenon.
1.deploy nexus in localhost:8081 like this
2.create a docker repository and config
3.config docker registry and restart "insecure-registries": [ "127.0.0.1:8082" ]
4.then try input in cmd $ docker login 127.0.0.1
get a response like this : Error response from daemon: Get "http://127.0.0.1:8082/v2/": dial tcp 127.0.0.1:8082: connect: connection refused
i click thr url "http://127.0.0.1:8082/v2/" and get a response like this;
{ "errors": [ { "code": "UNAUTHORIZED", "message": "access to the requested resource is not authorized", "detail": null } ] }
Result: I have already solved this question by modifing the ip 127.0.0.1 to my actual IPV4 address .
Does Anyone knows Why? Is it useful to analyze this issue using wireshark?
The text was updated successfully, but these errors were encountered:
Works fine in our e2e tests with Nexus: https://github.com/docker/build-push-action/actions/runs/6156437652/job/16705112653#step:10:35
Closing as this does not seem to be an issue with the action but registry's configuration.
Sorry, something went wrong.
No branches or pull requests
I met a phenomenon.
1.deploy nexus in localhost:8081 like this
2.create a docker repository and config
3.config docker registry and restart
"insecure-registries": [
"127.0.0.1:8082"
]
4.then try input in cmd
$ docker login 127.0.0.1
get a response like this :
Error response from daemon: Get "http://127.0.0.1:8082/v2/": dial tcp 127.0.0.1:8082: connect: connection refused
i click thr url "http://127.0.0.1:8082/v2/" and get a response like this;
{
"errors": [
{
"code": "UNAUTHORIZED",
"message": "access to the requested resource is not authorized",
"detail": null
}
]
}
Result:
I have already solved this question by modifing the ip 127.0.0.1 to my actual IPV4 address .
Does Anyone knows Why?
Is it useful to analyze this issue using wireshark?
The text was updated successfully, but these errors were encountered: