In swarm mode, the containers created do not join the overlay network (docker engine 29)

[sdunesme]

Hi team!

I am encountering an issue in Docker Swarm mode with the new docker engine version (29): the services created do not join the specified network (whether defined globally with proxy.docker.default-container-network or at the application level in container-network-connections). The problem occurs with Docker Engine 29, but everything works correctly with Docker Engine 28.
I should point out that shinyproxy itself runs in a containerized manner on the same docker swarm and with the same overlay network (sp-network).

Thank you for your fantastic work.

shinyproxy version = 3.2.2
docker-ce version = 29.0

spring:
  session:
    store-type: redis
  data:
    redis:
      host: redis

management:
  prometheus:
    metrics:
      export:
        enabled: true
        
proxy:
  body-classes:
   - shinyproxy-layout-grid
   - shinyproxy-layout-grid-4-columns
  title: MyTitle
  logo-url: https://mylogo
  same-site-cookie: Lax
  landing-page: /
  heartbeat-rate: 10000
  heartbeat-timeout: 60000
  port: 8080
  authentication: none
  store-mode: Redis
  stop-proxies-on-shutdown: false
  container-backend: docker-swarm
  hide-navbar: true
  usage-stats-url: micrometer
  docker:
    internal-networking: true
    port-range-start: 20000
    port-range-max: 21000
    image-pull-policy: Always
    service-wait-time: 180000
    default-container-network: sp-network

  specs:
    - id: app1
      display-name: "App1"
      logo-url: https://app1logo
      logo-width: 100%
      container-image: app1image:latest
      port: 8501
      container-network-connections:
        - sp-network
        - other-network
      container-volumes:
        - "/mnt/volumes/app1_data:/data"
      labels:
        version: 2
      container-env:
        ENV1: value1
        ENV2: value2
    - id: app2
      display-name: "App2"
      logo-url: https://app2logo
      logo-width: 100%
      container-image: app2image:latest
      port: 3800
      labels:
        version: 1
      container-env:
        ENV1: value1
        ENV2: value2

[LEDfan]

Hi, thanks for opening this issue!
Unfortunately, we missed this when making the release that fixes the other incompatibilities.
This is now fixed in the the docker image openanalytics/shinyproxy-snapshot:3.3.0-SNAPSHOT-20251205.082635 .
I hope it's okay for you to use a snapshot image. If more users are running into this (please let us known!) I can create a proper release for this.

[kirchner-symate]

I also ran (resp. am running) into the same problem. A proper release instead of the Snapshot would be really appreciated.
Addendum: The update within Release 3.3.0-SNAPSHOT did fix the problem for me.