Cyrill Troxler

I guess it would be possible but the whole deployment probably looks different plus the docker image would have to be built for running on windows. I don't have any...

Sorry for the late reply. If this is still relevant to you, can you please try the latest [pre-release](https://github.com/ctrox/csi-s3/releases/tag/v1.2.0-rc.1)? The old versions of csi-s3 were incompatible with Kubernetes 1.16+.

What Kubernetes version are you running and also what version of csi-s3 did you install? It seems like the `csi-provisioner` used is outdated.

Sorry for the super late reply. If this is somehow still relevant, I would recommend you build your own docker image on top of csi-s3 like `FROM ctrox/csi-s3:version` and then...

The driver implements the csi spec 1.0, so as long as nomad supports that it *should* work. I have not tried it, so I would just give it a shot...

No services are in use here, so that should not be a problem.

Yeah I'm aware of this. I'm looking for a workaround but this might be pretty difficult to solve as all the mounting happens in user space (fuse) and because of...

Can you have a look at the logs of the daemonset `csi-s3`? Because that should create the socket file on every node and allow the attacher to connect to it.

Sounds to me like a container runtime issue, not sure what is happening but docker seems unable to start the container. But that is for sure the root cause of...

It has been quite a while since I made that choice but the commit message [explains it](https://github.com/ctrox/csi-s3/commit/f80104f215d46b621328113b50bb6b325f34bb91) (although briefly). The main issue I can remember was that on every unclean...