kubernetes-sigs/aws-ebs-csi-driver

Does it work with docker 23.x with CSI support?

ieugen opened this issue · 7 comments

ieugen commented

Hi,

So docker 23.x was released with initial CSI support.
Is this the right place to "ask" about adding docker support for this plugin ?

Going through the issue It seems that CSI drivers should work out of the box if they are packaged for docker use.
See moby/moby#41982 (comment)

Basically, I've had to extract binaries from the images used by Kube or build those binaries from scratch and then build a Swarm CSI compatible Docker Plugin configuration. It's completely possible and doesn't require any changes in the CSI drivers, but I do have to start over from just the binaries.

There is some work relevant to this here https://github.com/olljanat/csi-plugins-for-docker-swarm

Release notes mention the github issues and what was released.
https://docs.docker.com/engine/release-notes/23.0/

Add experimental support for SwarmKit cluster volumes (CSI). moby/moby#41982
CLI: Add cluster volume (CSI) options to docker volume. docker/cli#3606
CLI: Add cluster volume (CSI) support to docker stack. docker/cli#3662

I am just a Docker user that would like to use EBS volumes with Docker.
I am opening this issue in the hope that it makes a difference.
I do imagine docker team can't handle everything on their own and it's something I would like to use.

Thanks,
Eugen

/triage support

k8s-ci-robot commented

@ieugen: The label(s) triage/support cannot be applied, because the repository doesn't have them.

In response to this:

Hi,

So docker 23.x was released with initial CSI support.
Is this the right place to "ask" about adding docker support for this plugin ?

Going through the issue It seems that CSI drivers should work out of the box if they are packaged for docker use.
See moby/moby#41982 (comment)

Basically, I've had to extract binaries from the images used by Kube or build those binaries from scratch and then build a Swarm CSI compatible Docker Plugin configuration. It's completely possible and doesn't require any changes in the CSI drivers, but I do have to start over from just the binaries.

There is some work relevant to this here https://github.com/olljanat/csi-plugins-for-docker-swarm

Release notes mention the github issues and what was released.
https://docs.docker.com/engine/release-notes/23.0/

Add experimental support for SwarmKit cluster volumes (CSI). moby/moby#41982
CLI: Add cluster volume (CSI) options to docker volume. docker/cli#3606
CLI: Add cluster volume (CSI) support to docker stack. docker/cli#3662

I am just a Docker user that would like to use EBS volumes with Docker.
I am opening this issue in the hope that it makes a difference.
I do imagine docker team can't handle everything on their own and it's something I would like to use.

Thanks,
Eugen

/triage support

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

ConnorJC3 commented

Hi @ieugen! Our driver is known to work on alternative container orchestrators such as Nomad and Cloud Foundry. As long as Docker Swarm implements the CSI specification correctly I see no reason the driver couldn't be used with it.

There is one downside: the driver needs to know what region it is running in. Today, we get that information from either IMDS or Kubernetes (we try both in parallel on startup). Obviously, when not running on Kubernetes that is not an option, so IMDS must be available to the driver to get the region from.

We likely won't provide any official documentation for Docker Swarm at the moment, but our official container image(s) are available in our README, and we have documentation about most of the driver's CLI paramaters. In theory, it should be as simple as setting up the driver using Docker's system.

Note that for obvious reasons we will not accept bug reports for non-standard quirks or bugs in Docker's implementation of CSI - those should be reported to the appropriate upstream. However, although our current bug report/feature request templates are geared towards Kubernetes we are willing to accept other issues as long as they are generally applicable to COs as a category rather than Docker Swarm specific.

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

torredil commented

/close

k8s-ci-robot commented

@torredil: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.