Niels de Vos

@bswartz or @saad-ali , is there still something to change here?

Contributions from someone that has tested it on Docker Swarm are still welcome!

There seems some interest in this feature. Most of the regular Ceph-CSI contributors are not familiar with Docker Swarm, so it is not something that they easily can do. Contributions...

Hmm, I always use Rook to deploy my Ceph cluster. But that obviously won't work if you want to use Docker Swarm instead of Kubernetes. The go-ceph project (https://github.com/ceph/go-ceph) runs...

Volunteers are still very welcome, check [this message](https://github.com/ceph/ceph-csi/issues/3769#issuecomment-1750202357) from @s4ke on how anyone can help.

The main `cephcsi` executable should provide many logs if it received the request to provision a volume. I am not familiar with Docker Swarm, but if you have error messages...

Hi @NymanRobin, You might be able to use `VolumeLocks` from `internal/util/idlocker.go` for locking too once you add a new `fscrypt` operation. Thanks for looking into this!

> Let me try to explain, so how I understand it is that the lock seems to be already acquired in the `NodStageVolume` on line 170, meaning that we already...

A lock that can time-out would be ideal, I guess. Depending on how complex you want to make it, this could be an approach: - obtain the lock 1. set...

> Hi @Madhu-1 @nixpanic. Should we use LockExclusive from ceph-go or the @NymanRobin's [current implementation](https://github.com/ceph/ceph-csi/pull/4688) is fine? The simpler it can be done, the better!