cli/compose: Handle Volume Subpath

[vvoland]

• fixes: don't work volume option subpath in docker swarm mode #5826

- Human readable description for the release notes

Fix Docker Swarm mode ignoring `volume.subpath`

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.18%. Comparing base (c542ad7) to head (add32e4).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5833   +/-   ##
=======================================
  Coverage   59.18%   59.18%           
=======================================
  Files         352      352           
  Lines       29547    29548    +1     
=======================================
+ Hits        17486    17487    +1     
  Misses      11080    11080           
  Partials      981      981           

[thaJeztah]

LGTM

[DivineJimmi]

I don't know nothing about github and stuff.
I am recently encountering the problem, that subpaths on swarm are not working.

Is this change already published? Do i get this feature, by simply updating my docker swarm? If not, how do i do it?

[vvoland]

Yes, this is already a part of Docker 28.0.0 (and up), so you just just update your Docker daemons.

[DivineJimmi]

I am using 28.0.1. But it is not working. Am i doing something wrong?

    volumes:
      - type: volume
        source: frigate
        target: /config
        volume:
          subpath: config
      - type: volume
        source: frigate
        target: /media/frigate
        volume:
          subpath: media/frigate

my container still writes to the volumes root directory..

[vvoland]

Have you recreated the containers?

[DivineJimmi]

If you mean deleting the old containers and creating a new one, by deploying the stack - yes.

I also recreated the volume and added subdirectories via mkdir.

I use docker swarm on multiple RasPis. The stack is only deployed on one single node. The volume is on that same node.

Frigate also writes to the volume just fine. But it ignores the subdirectories.

[pvledoux]

I have a similar issue with Docker version 28.0.4, build b8034c0. I have a cifs volume created as stacks-data. When I run this compose file, it creates a /caddy in the root directory of the stacks-data volumes, and the test.txt is created in the root too:

version: '3'
services:
  web:
    image: caddy:latest
    volumes:
      - type: volume
        source: stacks-data
        target: /config
        volume:
          subpath: /prod/caddy/config
      - type: volume
        source: stacks-data
        target: /data
        volume:
          subpath: /prod/caddy/data
      - type: volume
        source: stacks-data
        target: /var/www/public/storage
        volume:
          subpath: /prod/data/app/public
    command: |
            touch /var/www/public/storage/test.txt

volumes:
  stacks-data:
    external: true