name Additional property name is not allowed

[itstarlab]

This is my first time using this, so I may be doing something wrong, but it doesn't feel like so.
I have installed GlusterFS in a 3 node swarm.
It works well, and the services can use the volumes as bind volumes.
I have installed the plugin, following the instructions, but when I try to build with compose or deploy to the stack I get:

docker stack deploy -c docker-compose.yml whatever
name Additional property name is not allowed

Example used docker-compose.yml:

`version: 3

services:

postgres:
image: "mdillon/postgis"
deploy:
replicas: 1
restart_policy:
condition: on-failure
delay: 5s
container_name: postgres
ports:
- "4321:5432"
volumes:
- pgdata:/var/lib/postgresql/data

volumes:
pgdata:
driver: glusterfs
name: "swarmVolume"
`
And this is the output for the swarmVolume info

Volume Name: swarmVolume Type: Replicate Volume ID: 76275e72-6e85-48c2-a8dd-21e8dfce8ed4 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: Swarm-Master:/gluster/volume1 Brick2: Swarm-Manager-1:/gluster/volume1 Brick3: Swarm-Manager-2:/gluster/volume1 Options Reconfigured: transport.address-family: inet storage.fips-mode-rchecksum: on nfs.disable: on performance.client-io-threads: off

docker info:

`Client:
Debug Mode: false

Server:
Containers: 4
Running: 3
Paused: 0
Stopped: 1
Images: 29
Server Version: 19.03.12
Storage Driver: overlay2
Backing Filesystem: extfs
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: 9vnjz1h7r1agru5g132skjk
Is Manager: true
ClusterID: p0wpqg412gkeln21tmvddom
Managers: 3
Nodes: 3
Default Address Pool: 1.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: 1.0.0.1
Manager Addresses:
1.0.0.1:2377
1.0.0.2:2377
1.0.0.3:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9be36df0a9dd
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.15.0-109-generic
Operating System: Ubuntu 18.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.852GiB
Name: Swarm-Master
ID: ZHPJ:UJW:JDDO:L4WN:LUDX:SGI:ZLLH:INPF:F5UY:J35Z:MLOH:4PP
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: No swap limit support`

Also, Is it possible to use this plugin from within gitlab-runner? So one can integrate with CI/CD, and build images aware of GlusterFS, and deploy to production.

[khalidchamakh]

Hi, You can use 3.4 compose

[kevinpawsey]

had this issue, and this worked for me, just changed the compose version from 3.2 > 3.4

thank you @elbissat