Container with publish mode ingress not starting

[CMALG]

Description

Good day,

i think i have found a bug otherwise i can't explain this behavior.
Just a little bit context. This is container running a simple tftp server.
But for some reason only on my setup there are some breaking issues.

Reproduce

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

Expected behavior

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

this does start perfectly fine

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

docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.2-docker)
  compose: Docker Compose (Docker Inc., v2.6.0)

Server:
 Containers: 4
  Running: 4
  Paused: 0
  Stopped: 0
 Images: 5
 Server Version: 20.10.17
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 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: active
  NodeID: ye2so42jcgr6z9ldmz2xhewr7
  Is Manager: true
  ClusterID: 3galdkfv48nwtq7uxdlrnxcwx
  Managers: 1
  Nodes: 2
  Default Address Pool: 10.0.0.0/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: 192.168.3.100
  Manager Addresses:
   192.168.3.100:2377
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc version: v1.1.2-0-ga916309
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.15.0-1013-raspi
 Operating System: Ubuntu 22.04.1 LTS
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 905.2MiB
 Name: Manager-1
 ID: V65I:2PT3:EIBQ:IKVT:MQZQ:EDME:WKLU:JTY4:UUJW:ECX3:ZY66:TJ2C
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional Info

Some other wierd issues persist with this setup. For example if i run the same setup in a stack i get wierd permission errors which do not appear when i run the container with the "Expected behavior" setup.
So something breaks if i switch to ingress. But strangely it does start as a stack.

[sam-thibault]

When running with ingress, you may have an issue if the port is already in use on any of the nodes in the swarm. Can you verify whether the port is already in use? Can you also share the actual error message?

[bsousaa]

It looks like this issue went stale. Let me close it for now. Feel free to comment and we can re-open if we have more info.