docker stack deploy with error 'unsupported Compose file version: 1.0'

[ewerton-silva00]

Description

Error executing the command below:

docker stack deploy --compose-file docker-compose.yml name

Result of the above command:

unsupported Compose file version: 1.0

Output docker version:

Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:27:04 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:25:42 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output docker info:

Client:
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 19.03.8
 Storage Driver: overlay2
  Backing Filesystem: <unknown>
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 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: mrytny5tvrk8vodlz1vsu1laa
  Is Manager: true
  ClusterID: f4krmkfcwvwkcnjl87xw2k3yw
  Managers: 2
  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: 10.10.2.101
  Manager Addresses:
   10.10.2.101:2377
   10.10.2.102:2377
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 3.10.0-1062.18.1.el7.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 1.794GiB
 Name: manager-01.esig.com.br
 ID: 5MJ2:4X5U:5TD6:6Y2G:VR6G:UZ5X:GHQN:FGIX:O7QM:Y7N2:UUTS:GNWA
 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

WARNING: bridge-nf-call-ip6tables is disabled
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.

Compose file version:

3.8

Additional environment details:

CentOS Linux release 7.8.2003 (Core)
3.10.0-1062.18.1.el7.x86_64
Note: virtualized server with kvm

[rasmustwh]

Sounds to me, like a misconfigured compose file, but it's hard to tell without more details.

[thaJeztah]

Yes, without more details, I don't see anything actionable here. Let me close this one

[s7726]

Using the latest docker (version 20.10.5, build 55c4c88) and docker-compose (version 1.29.1) a stack deployment complains if there is no version number in the yaml (complains of version 1), but doesn't recognize the depends_on conditions as defined in the latest compose spec if the version is 3.8.

[smidge84]

This issue is related to #2527.

@ewerton-silva00 It seems like you have the same process that I do, which lead to me opening my own issue #9133.

[thaJeztah]

I think #3257 will fix this case (it doesn't switch to the compose-spec, but will work with compose-files that use options supported by v3)

[smidge84]

HI @thaJeztah,

Thanks for the update. Based on the title, it might do.
Certainly I can try it out some time to see.

I'll keep an eye on that Pull Request.