I’m new to docker and docker swarm and i’m stuck with a really strange issue.
When creating a service with a simple tftp container for some reason it’s impossible to get it working with an ingress overlay network, host mode is totally fine and works.
OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-1013-raspi aarch64)
Docker Version:
Client: Docker Engine - Community
Version: 20.10.17
API version: 1.41
Go version: go1.17.11
Git commit: 100c701
Built: Mon Jun 6 23:02:17 2022
OS/Arch: linux/arm64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.17
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: a89b842
Built: Mon Jun 6 23:00:41 2022
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.6
GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc:
Version: 1.1.2
GitCommit: v1.1.2-0-ga916309
docker-init:
Version: 0.19.0
GitCommit: de40ad0
It’s running on a two node swarm with a raspberry pi 3b+ and 4.
This does start and work
docker service create \
--mode global \
--publish mode=host,target=69,published=69,protocol=udp \
--name=tftp \
-e TZ="Europe/Berlin" \
-e CREATE=1 \
3x3cut0r/tftpd-hpa:latest
If you change publish mode to ingress the containers are stuck in “new” and will never start, waited hours…
docker service create \
--mode global \
--publish mode=ingress,target=69,published=69,protocol=udp \
--name=tftphost \
-e TZ="Europe/Berlin" \
-e CREATE=1 \
3x3cut0r/tftpd-hpa:latest
Is that a limitation of any kind i’m not aware of ? Any ideas ?
Your last command works like a charme on Ubuntu 20.04 with the same docker-ce version on x86_64.
Could be kernel differences… or be a bug in the docker-ce arm version …
You could check if your kernel supports all required modules:
Hey there, I’m bumping into the same issue on docker 23.0.1 on rpi with ubuntu 22.04 64bit and wondering if you managed to figure out what this issue is and whether you found a way around it, or filed a bug.