You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "JK-97 (via GitHub)" <gi...@apache.org> on 2023/09/06 08:57:11 UTC

[GitHub] [apisix] JK-97 opened a new issue, #10167: Confuse : apisix cannot successfully proxy registry2(docker)

JK-97 opened a new issue, #10167:
URL: https://github.com/apache/apisix/issues/10167

   ### Current Behavior
   
   1. deploy apisix,and registry
   2. add a route ,172.16.19.222:5000 host a regstry2 server
   ```
   curl --location --request PUT 'http://172.16.10.222:9180//apisix/admin/routes' \
   --header 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' \
   --header 'Content-Type: application/json' \
   --data '{
       "id": "getting-started-ip",
       "uri": "/v2/*",
       "upstream": {
           "type": "roundrobin",
           "nodes": {
               "172.16.10.222:5000": 1
           }
       }
   }'
   ```
   3. docker push 
   ```
   ╰─$ docker push  172.16.10.222:9080/test/al                                                                                  130 ↵
   Using default tag: latest
   The push refers to repository [172.16.10.222:9080/test/a]
   27febb3ceff7: Pushing [==================================================>]  4.872MB
   error parsing HTTP 403 response body: invalid character 'c' looking for beginning of value: "connecting to 172.16.10.222:80: connecting to 172.16.10.222:80: dial tcp 172.16.10.222:80: connect: connection refused"
   ```
   On the contrary, I deployed nginx alone for implementation and it was successful
   
   ### Expected Behavior
   
   docker push sucess.
   Not possible **connecting to 172.16.10.222:80:**
   
   ### Error Logs
   
   
   docker daemon logs :
   ```
   [2023-09-06T08:49:06.295081376Z][dockerd][I] time="2023-09-06T08:49:06.294466626Z" level=debug msg="Trying to push 172.16.10.222:9080/test/a to http://172.16.10.222:9080 v2"
   [2023-09-06T08:49:06.320065835Z][dockerd][I] time="2023-09-06T08:49:06.319883335Z" level=debug msg="Pushing repository: 172.16.10.222:9080/test/a:latest"
   [2023-09-06T08:49:06.320604543Z][dockerd][I] time="2023-09-06T08:49:06.320442210Z" level=debug msg="Checking for presence of layer sha256:27febb3ceff77486349658d0c6f1c00bc9459f39ea41dfc14fd42a37895a4e87 (sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d) in 172.16.10.222:9080/test/a"
   [2023-09-06T08:49:06.339135585Z][dockerd][I] time="2023-09-06T08:49:06.338942168Z" level=debug msg="Pushing layer: sha256:27febb3ceff77486349658d0c6f1c00bc9459f39ea41dfc14fd42a37895a4e87"
   [2023-09-06T08:49:06.365725002Z][dockerd][I] time="2023-09-06T08:49:06.365415460Z" level=debug msg="Assembling tar data for b105214618d3331f496501499b1f6eadf8795573a14530fa5c4915c78639742e"
   [2023-09-06T08:49:06.545833210Z][dockerd][I] time="2023-09-06T08:49:06.545611085Z" level=error msg="Upload failed: error parsing HTTP 403 response body: invalid character 'c' looking for beginning of value: \"connecting to 172.16.10.222:80: connecting to 172.16.10.222:80: dial tcp 172.16.10.222:80: connect: connection refused\""
   [2023-09-06T08:49:06.545843543Z][dockerd][I] time="2023-09-06T08:49:06.545644918Z" level=info msg="Attempting next endpoint for push after error: error parsing HTTP 403 response body: invalid character 'c' looking for beginning of value: \"connecting to 172.16.10.222:80: connecting to 172.16.10.222:80: dial tcp 172.16.10.222:80: connect: connection refused\""
   ```
   
   apisix logs:
   ```
   172.16.30.210 - - [06/Sep/2023:08:49:06 +0000] - "\x16\x03\x01\x00\xDA\x01\x00\x00\xD6\x03\x03\x9A\x83<" 400 229 0.005 "-" "-" - - - "://"
   172.16.30.210 - - [06/Sep/2023:08:49:06 +0000] 172.16.10.222:9080 "GET /v2/ HTTP/1.1" 200 2 0.007 "-" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \x5C(darwin\x5C))" 172.16.10.222:5000 200 0.007 "http://172.16.10.222:9080"
   172.16.30.210 - - [06/Sep/2023:08:49:06 +0000] 172.16.10.222:9080 "HEAD /v2/test/a/blobs/sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d HTTP/1.1" 404 0 0.005 "-" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \x5C(darwin\x5C))" 172.16.10.222:5000 404 0.005 "http://172.16.10.222:9080"
   172.16.30.210 - - [06/Sep/2023:08:49:06 +0000] 172.16.10.222:9080 "POST /v2/test/a/blobs/uploads/ HTTP/1.1" 202 0 0.009 "-" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \x5C(darwin\x5C))" 172.16.10.222:5000 202 0.010 "http://172.16.10.222:9080"
   ```
   
   
   registry2 logs :
   ```
   time="2023-09-06T08:49:06.275489556Z" level=info msg="response completed" go.version=go1.19.9 http.request.host="172.16.10.222:9080" http.request.id=dc4244fd-5aa8-49fb-9ac7-549bbafae608 http.request.method=GET http.request.remoteaddr=172.16.30.210 http.request.uri="/v2/" http.request.useragent="docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \(darwin\))" http.response.contenttype="application/json; charset=utf-8" http.response.duration=2.575144ms http.response.status=200 http.response.written=2
   172.17.0.1 - - [06/Sep/2023:08:49:06 +0000] "GET /v2/ HTTP/1.1" 200 2 "" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \\(darwin\\))"
   time="2023-09-06T08:49:06.296087253Z" level=error msg="response completed with error" err.code="blob unknown" err.detail=sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d err.message="blob unknown to registry" go.version=go1.19.9 http.request.host="172.16.10.222:9080" http.request.id=c0354f1e-5371-4ba6-9247-05983fe10d39 http.request.method=HEAD http.request.remoteaddr=172.16.30.210 http.request.uri="/v2/test/a/blobs/sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d" http.request.useragent="docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \(darwin\))" http.response.contenttype="application/json; charset=utf-8" http.response.duration=2.312888ms http.response.status=404 http.response.written=157 vars.digest="sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d" vars.name="test/a"
   172.17.0.1 - - [06/Sep/2023:08:49:06 +0000] "HEAD /v2/test/a/blobs/sha256:2a3ebcb7fbcc29bf40c4f62863008bb573acdea963454834d9483b3e5300c45d HTTP/1.1" 404 157 "" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \\(darwin\\))"
   time="2023-09-06T08:49:06.320536139Z" level=info msg="response completed" go.version=go1.19.9 http.request.host="172.16.10.222:9080" http.request.id=bba9777c-1442-47f8-b420-6e733011effb http.request.method=POST http.request.remoteaddr=172.16.30.210 http.request.uri="/v2/test/a/blobs/uploads/" http.request.useragent="docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \(darwin\))" http.response.duration=7.604852ms http.response.status=202 http.response.written=0
   172.17.0.1 - - [06/Sep/2023:08:49:06 +0000] "POST /v2/test/a/blobs/uploads/ HTTP/1.1" 202 0 "" "docker/20.10.23 go/go1.18.10 git-commit/6051f14 kernel/5.15.49-linuxkit os/linux arch/arm64 UpstreamClient(Docker-Client/20.10.23 \\(darwin\\))"
   ```
   
   ### Steps to Reproduce
   
   just like above "Current Behavior"
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix] JK-97 commented on issue #10167: help request : apisix cannot successfully proxy registry2(docker)

Posted by "JK-97 (via GitHub)" <gi...@apache.org>.
JK-97 commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1713307190

   @Revolyssup 
   of course,it tagged。
   register2 server generated logs


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "Revolyssup (via GitHub)" <gi...@apache.org>.
Revolyssup commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1859500130

   can't reproduce.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "Revolyssup (via GitHub)" <gi...@apache.org>.
Revolyssup closed issue #10167: help request : apisix cannot successfully proxy registry2(docker)
URL: https://github.com/apache/apisix/issues/10167


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "shreemaan-abhishek (via GitHub)" <gi...@apache.org>.
shreemaan-abhishek commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1859229716

   @sheharyaar, the issue threads that you mentioned are fairly lengthy, would you like to add a summary about what those issues talk about?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix] Revolyssup commented on issue #10167: help request : apisix cannot successfully proxy registry2(docker)

Posted by "Revolyssup (via GitHub)" <gi...@apache.org>.
Revolyssup commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1711211894

   @JK-97 Did you first tag the image with the host name or IP address, and the port of the registry?
   `docker image tag a:latest 172.16.10.222:9080/test/a:latest`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "sheharyaar (via GitHub)" <gi...@apache.org>.
sheharyaar commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1853324335

   @JK-97 any update with this issue ? I would like you to checkout : https://github.com/distribution/distribution/issues/2746
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "sheharyaar (via GitHub)" <gi...@apache.org>.
sheharyaar commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1853358064

   Also , please checkout this too : https://github.com/distribution/distribution/issues/2225


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request : apisix cannot successfully proxy registry2(docker) [apisix]

Posted by "sheharyaar (via GitHub)" <gi...@apache.org>.
sheharyaar commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1851387558

   @shreemaan-abhishek , I would like to look into this.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [apisix] JK-97 commented on issue #10167: help request : apisix cannot successfully proxy registry2(docker)

Posted by "JK-97 (via GitHub)" <gi...@apache.org>.
JK-97 commented on issue #10167:
URL: https://github.com/apache/apisix/issues/10167#issuecomment-1707954576

   pls help


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org