You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/05/31 07:36:42 UTC
[GitHub] [apisix-ingress-controller] stillfox-lee opened a new issue, #1059: e2e-test: kind local registry network problem
stillfox-lee opened a new issue, #1059:
URL: https://github.com/apache/apisix-ingress-controller/issues/1059
Issue:
When I use `make e2e-test-local`, docker push always fails with a timeout. But the network connection was work well.
```
❯ docker push localhost:5000/apache/apisix
Using default tag: latest
The push refers to repository [localhost:5000/apache/apisix]
Get "http://localhost:5000/v2/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
❯ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7bbe20a61254 registry:2 "/entrypoint.sh /etc…" 6 minutes ago Up 6 minutes 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp kind-registry
❯ curl "http://localhost:5000/v2/"
{}%
```
Then, I dig into the script `kind-with-registry.sh` and find out something:
First, it created a new registry by:
```
docker run \
-d --restart=always -p "${reg_port}:5000" --name "${reg_name}" \
registry:2
```
When registry was created, it forword ipv4 only:
```
❯ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7bbe20a61254 registry:2 "/entrypoint.sh /etc…" 6 minutes ago Up 6 minutes 0.0.0.0:5000->5000/tcp kind-registry
```
After the script execute `docker network connect "${kind_network}" "${reg_name}"`. The registry container will forword both ipv4 and ipv6:
```
❯ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7bbe20a61254 registry:2 "/entrypoint.sh /etc…" 6 minutes ago Up 6 minutes 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp kind-registry
```
If registry container forward ipv4 only, docker push will work. If it forward both ipv4 and ipv6. Docker push will timeout.
My environment:
system: macOS 12.0.1
docker:
```
❯ docker version
Client:
Cloud integration: v1.0.24
Version: 20.10.14
API version: 1.41
Go version: go1.16.15
Git commit: a224086
Built: Thu Mar 24 01:49:20 2022
OS/Arch: darwin/arm64
Context: default
Experimental: true
Server: Docker Desktop 4.8.2 (79419)
Engine:
Version: 20.10.14
API version: 1.41 (minimum version 1.12)
Go version: go1.16.15
Git commit: 87a90dc
Built: Thu Mar 24 01:45:44 2022
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.5.11
GitCommit: 3df54a852345ae127d1fa3092b95168e4a88e2f8
runc:
Version: 1.0.3
GitCommit: v1.0.3-0-gf46b6ba
docker-init:
Version: 0.19.0
GitCommit: de40ad0
```
kind:
```
❯ kind version
kind v0.13.0 go1.17.3 darwin/arm64
```
--
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-ingress-controller] tao12345666333 commented on issue #1059: e2e-test: kind local registry network problem
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1059:
URL: https://github.com/apache/apisix-ingress-controller/issues/1059#issuecomment-1146749436
> If registry container forward ipv4 only, docker push will work. If it forward both ipv4 and ipv6. Docker push will timeout.
can you check your `/etc/hosts` file? or try to use `127.0.0.1` instead of `localhost`
--
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-ingress-controller] stillfox-lee closed issue #1059: e2e-test: kind local registry network problem
Posted by GitBox <gi...@apache.org>.
stillfox-lee closed issue #1059: e2e-test: kind local registry network problem
URL: https://github.com/apache/apisix-ingress-controller/issues/1059
--
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-ingress-controller] stillfox-lee commented on issue #1059: e2e-test: kind local registry network problem
Posted by GitBox <gi...@apache.org>.
stillfox-lee commented on issue #1059:
URL: https://github.com/apache/apisix-ingress-controller/issues/1059#issuecomment-1141926351
> @stillfox-lee can you paste your `docker info` command output?
Sure.
```
❯ docker info
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.8.2)
compose: Docker Compose (Docker Inc., v2.5.1)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.17.0)
Server:
Containers: 6
Running: 5
Paused: 0
Stopped: 1
Images: 25
Server Version: 20.10.14
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8
runc version: v1.0.3-0-gf46b6ba
init version: de40ad0
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.10.104-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 7.765GiB
Name: docker-desktop
ID: I3HW:FVUG:OJ3O:GJL6:FMZA:Q2VT:G74L:PKZQ:MYWJ:AWRW:RGR2:JAVC
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
```
--
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-ingress-controller] tao12345666333 commented on issue #1059: e2e-test: kind local registry network problem
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1059:
URL: https://github.com/apache/apisix-ingress-controller/issues/1059#issuecomment-1141913430
@stillfox-lee can you paste your `docker info` command output?
--
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-ingress-controller] stillfox-lee commented on issue #1059: e2e-test: kind local registry network problem
Posted by GitBox <gi...@apache.org>.
stillfox-lee commented on issue #1059:
URL: https://github.com/apache/apisix-ingress-controller/issues/1059#issuecomment-1146831441
I use
```
docker run \
-d --restart=always -p "127.0.0.1:${reg_port}:5000" --name "${reg_name}" \
registry:2
```
instead of
```
docker run \
-d --restart=always -p "${reg_port}:5000" --name "${reg_name}" \
registry:2
```
The local registry container will bind 127.0.0.1:5000 only. Then docker push can work correctly.
Thanks for your reply! @tao12345666333
--
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