cannot fulfill requested CSI volume mounts on 1 node
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Hey guys,
So I was trying to setup Docker Swarm cluster with CSI plugin (ghcr.io/cloud-skeleton/democratic-csi-swarm).
I have installed it on all nodes:
ID NAME DESCRIPTION ENABLED
2a8d168b768a democratic-csi-swarm:latest Democratic CSI plugin for Docker Swarm true
On manager node I can create volume directly with cli:
docker volume create \
-d democratic-csi-swarm \
--group system \
--label eu.cloudskeleton.volume=true \
--label eu.cloudskeleton.volume.type=system \
--scope multi \
--sharing all \
--required-bytes 10737418240 \
--topology-required eu.cloudskeleton.node=true \
proxy
and all's good, HOWEVER I have tried everything and I can not achieve same result with compose.yml:
services:
test:
...
volumes:
- source: proxy
target: /data/traefik/configs
type: cluster
volumes:
proxy:
driver: democratic-csi-swarm
driver_opts:
group: system
required-bytes: 10737418240
scope: multi
sharing: all
topology-required: eu.cloudskeleton.node=true
labels:
eu.cloudskeleton.volume: "true"
eu.cloudskeleton.volume.type: system
Deployment would always fail with:
cannot fulfill requested CSI volume mounts on 1 node
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure from the provided compose.yml and compare it with the working docker volume create command. Trace how the compose volume options and topology requirement become the requested CSI volume mounts, then verify that deployment no longer reports "cannot fulfill requested CSI volume mounts on 1 node".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100