GlusterFS support in Container Linux?

[Kevin Heatwole]

My file servers have 2 large HDDs locally that I would like to manage with GlusterFS (so the 3 file servers mount the GlusterFS volumes on each server).

Does Container Linux support running GlusterFS to manage the local storage available on the local servers? And, can I mount the volumes using the Gluster client?

Or, do I need to run some other Linux distribution on my file servers and forget about Container Linux?

[Brandon Philips]

You should be able to run glusterfs on Container Linux; we have a prototype project for Kubernetes that is doing just that called quartermaster.

Have you tried to run gluster and hit issues?

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kevin Heatwole]

On Monday, April 3, 2017 at 6:57:18 PM UTC-4, Brandon Philips wrote:

You should be able to run glusterfs on Container Linux; we have a prototype project for Kubernetes that is doing just that called quartermaster.

Have you tried to run gluster and hit issues?

No, but I decided against using Container Linux for my project because Container Linux does not include the glusterfs client for mounting gluster volumes on the Docker host and its lagging support for upgrading Docker to the latest versions (Stable and Beta channels are still using 1.12.6 which is very old, especially for Swarm users, and the Alpha channel hasn't upgraded to docker-ce yet either). I feel that CoreOS is moving away from Docker in favor of Kubernetes so I doubt support for Docker Swarm is getting much effort within CoreOS. So, I think it is best not to commit to Container Linux for this project.

I will probably run Debian 9 or Ubuntu 17.04 on the Docker hosts and re-consider Container Linux for future projects if they require Kubernetes (unlikely in my case).

[Brandon Philips]

Hey Kevin-

Part of the problem we are having is that people are having different versions of Docker that they need to use based on if they are using Kubernetes, Swarm, or something else. To that end we have started experimenting with ways of letting users pin and select their version of Docker: https://github.com/coreos/docker-skim

We understand the frustration and are trying to do the best by our users knowing that the near future might mean multiple versions of Docker that are "right" depending on the users desired use.

Cheers,

Brandon

[Kevin Heatwole]

On Monday, April 3, 2017 at 7:51:54 PM UTC-4, Brandon Philips wrote:

Hey Kevin-

Part of the problem we are having is that people are having different versions of Docker that they need to use based on if they are using Kubernetes, Swarm, or something else. To that end we have started experimenting with ways of letting users pin and select their version of Docker: https://github.com/coreos/docker-skim

We understand the frustration and are trying to do the best by our users knowing that the near future might mean multiple versions of Docker that are "right" depending on the users desired use.

I understand and it is reasonable that Container Linux only include 1.12.6 in the Stable and Beta channels since Kubernetes needs added time to support the latest Docker updates and Kubernetes doesn't really require any of the recent features added by Docker. I would imagine that at some point, Kubernetes will stop depending on Docker and use Docker's containerd (when it goes 1.0?) or even switch to CoreOS Rocket as the preferred container manager. Then, Container Linux would be able to include the latest version of Docker (and move this latest version quickly through to the Stable channel for production use).