Hi Wayne,
today I found a few minutes to create a test app setup:
(1) network must be gigabit (with less it won’t crash the eqos)
(2) you’ll need traefik and a python3 container (see below)
I didn’t manage to create the issue without traefik in-between but I am positive, that the issue is not 100% related to traefik, as others observed it in other setups - probably traefik is doing “something” to the network packages which increased the chances of breaking stuff.
First of all: the dmesg (79.2 KB)
I’d need some more time to prepare an easy-to-launch environment, but here, you’ll find the python3 server/client which are flooding the ring-buffer (I run server on jetson behind traefik and the client on my laptop, single server, single client) and the traefik environment comes from dockerhub: traefik:v2.3 and configured like below. I think this should be easy to set up on your side?
version: "3.5"
services:
proxy:
image: "traefik:v2.3"
container_name: "traefik"
restart: always
command:
#- "--log.level=DEBUG"
#- "--api.insecure=true"
- "--providers.docker=true"
- "--providers.docker.exposedbydefault=false"
- "--entrypoints.web.address=:80"
- "--entrypoints.grpc.address=:8888"
networks:
- mynet
ports:
- "80:80"
- "8888:8888"
#- "8080:8080" # dashboard
volumes:
- "/var/run/docker.sock:/var/run/docker.sock:ro"
networks:
mynet:
external: true
For the sample server, you’ll need some additional labels in your docker-compose, you could use the 3dvl/jupyter docker image, as it has the python dependencies installed - or use any other python3 and install numpy and grpcio-tools manually.
labels:
- "traefik.enable=true"
- "traefik.http.routers.stereo.rule=Headers(`app`, `stereo`) && Headers(`content-type`, `application/grpc`)"
- "traefik.http.routers.stereo.entryPoints=grpc"
- "traefik.http.services.stereo.loadBalancer.server.port=51346"
- "traefik.http.services.stereo.loadBalancer.server.scheme=h2c"
Hope that helps? If you need further assistance to reproduce, please let me know.
Best,
Axel