[BUG] 2.26.1 does not allow resources.limits.cpu to be a number

[deubert-it]

Description

We used docker-compose 2.25.0 before (debian 11 default package), and after the upgrade to 2.26.1 (current debian 11 stable package as of last night) our stack deployments fail with something like "services.agent.deploy.resources.limits.cpus must be a string"

We usually do something like docker compose config | .. | docker stack deploy, this worked with 2.25.0 but does not work with 2.26.1 anymore.

I checked the compose spec and it still seems to allow "number", "string": https://github.com/compose-spec/compose-spec/blob/master/schema/compose-spec.json#L519

Steps To Reproduce

config:

version: '3.8'
services:
  agent:
    deploy:
      mode: global
      resources:
        limits:
          cpus: 0.5
          memory: "268435456"
        reservations:
          cpus: 0.1
          memory: "67108864"
      placement:
        constraints:
          - node.platform.os == linux
    image: portainer/agent:2.20.1
    networks:
      master_agent_network: null
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
        bind:
          create_host_path: true
      - type: bind
        source: /var/lib/docker/volumes
        target: /var/lib/docker/volumes
        bind:
          create_host_path: true

Trying to deploy this via docker stack deploy will result in "services.agent.deploy.resources.limits.cpus must be a string" and the deployment will fail.

Compose Version

Docker Compose version v2.26.1

docker-compose version
-bash: docker-compose: command not found

Docker Environment

Client: Docker Engine - Community
 Version:    26.0.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.13.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.26.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 18
  Running: 17
  Paused: 0
  Stopped: 1
 Images: 37
 Server Version: 26.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
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: active
  NodeID: XXX
  Is Manager: true
  ClusterID: XXX
  Managers: 3
  Nodes: 5
  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: xxx
  Manager Addresses:
   xxx:2377
   yyy:2377
   zzz:2377
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.10.0-28-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.62GiB
 Name: XXX
 ID: XXX
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

### Anything else?

_No response_

[glours]

Hey @deubert-it
I used your compose file with Compose config

> docker compose -f tmp config                                                                                                                                                                                      node system 09:52:08
WARN[0000] /Users/glours/tmp/tmp: `version` is obsolete
name: tmp
services:
  agent:
    deploy:
      mode: global
      resources:
        limits:
          cpus: 0.5
          memory: "268435456"
        reservations:
          cpus: 0.1
          memory: "67108864"
      placement:
        constraints:
          - node.platform.os == linux
    image: portainer/agent:2.20.1
    networks:
      master_agent_network: null
    volumes:
      - type: bind
        source: /var/run/docker.sock
        target: /var/run/docker.sock
        bind:
          create_host_path: true
      - type: bind
        source: /var/lib/docker/volumes
        target: /var/lib/docker/volumes
        bind:
          create_host_path: true
networks:
  master_agent_network:
    name: tmp_master_agent_network

And as you can see compose doesn't complains about your compose file, but swarm will as it doesn't follow the Compose Specification.

> docker stack deploy --compose-file tmp test                                                                                                                                                                       node system 09:59:47
services.agent.deploy.resources.limits.cpus must be a string

You can open an issue in this repository https://github.com/docker/cli

[deubert-it]

Hi @glours,
thank you for your quick response!