Swarm ports not listed


My swarm demo cluster is not publishing ports as expected.
Having the following compose file, it doesn’t show published ports on swarm. Should I file a bug?

version: '3.8'
    image: 'rsyslog:22.04'
     - '514:514/udp'
      - ./rsyslog.conf:/etc/rsyslog.conf
      - ../../data/:/data/
      - /var/log/:/logs/
docker stack deploy -c rsyslog-stack.yml rsyslog
 CONTAINER ID   IMAGE           COMMAND                  CREATED         STATUS         PORTS     NAMES
 5639da2e9909   rsyslog:22.04   "/bin/sh -c 'rsyslog…"   9 minutes ago   Up 9 minutes             rsyslog_rsyslog.1.vs6r1idjptmn14y9fy0qts46o


FROM ubuntu:22.04
RUN apt update && apt -y install software-properties-common
RUN add-apt-repository -y ppa:adiscon/v8-stable
RUN apt update && apt -y install rsyslog-relp rsyslog-mmjsonparse liblognorm5
CMD rsyslogd -n

docker -v:

Docker version 23.0.1, build a5ee5b1

docker info:

 Context:    default
 Debug Mode: false
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.2
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.16.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose
  scan: Docker Scan (Docker Inc.)
    Version:  v0.23.0
    Path:     /usr/libexec/docker/cli-plugins/docker-scan

 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 10
 Server Version: 23.0.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: j73xhnnoog7rl9zngena01g0h
  Is Manager: true
  ClusterID: tthbncu84qm3po4rgiy3g269u
  Managers: 2
  Nodes: 2
  Default Address Pool:  
  SubnetSize: 24
  Data Path Port: 4789
   Task History Retention Limit: 5
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address:
  Manager Addresses:
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 2456e983eb9e37e47538f59ea18f2043c9a73640
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
   Profile: builtin
 Kernel Version: 5.15.0-30-generic
 Operating System: Ubuntu 22.04.1 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 3.833GiB
 Name: vmdocker-mz-02
 ID: 2658d432-db92-4c1a-9344-1bf7f64b6387
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Experimental: false
 Insecure Registries:
 Live Restore Enabled: false

WARNING: Running Swarm in a two-manager configuration. This configuration provides
         no fault tolerance, and poses a high risk to lose control over the cluster.
         Refer to https://docs.docker.com/engine/swarm/admin_guide/ to configure the
         Swarm for fault-tolerance.

Solved EXPOSING ports on Dockerfile. Seems custom images without EXPOSED ports are not listed on docker ps.

The expectation is incorrect: the port is published on the service, not on the container.
Try docker service ps rsyslog_rsyslog