gluster-containers
gluster-containers copied to clipboard
gluster
GlusterClient container crashes, no logs
See Title
GlusterClient has no documentation in this repo.
Launched in Docker/Kubernetes and crashes with no messaging/logs to suggest why.
Also happen in centos 7 glusterfs 6.10. Don't know which container cause this. Been using over 6 month without problem ( not doing any update to the os and library ). Then suddenly it kept breaking. Will updating to 9.4 fix the problem ?
which version of glusterfs are you using?
glusterfs-client:Latest which as [per the repo is running v3.13]9https://github.com/gluster/gluster-containers/issues/176#issuecomment-945064582
Possibly issue gluster/glusterfs#2467
Maybe... My issue is that the container crashes on start, and provides no logs. I can't see if you are using the server or client containers in your issue.
Also happen in centos 7 glusterfs 6.10. Don't know which container cause this. Been using over 6 month without problem ( not doing any update to the os and library ). Then suddenly it kept breaking. Will updating to 9.4 fix the problem ?
Dunno... But given that this repo/container(s) are capped at Gluster v3.13 on the latest tag, I would not look for your solutions here.
My only "solution" for a containerized GlusterFS v9.x+ is to go built it myself: https://github.com/GoingOffRoading/GlusterFS
Just started this AM, will have a basic dockerfile/image to pull later today
@GoingOffRoading see if kadalu project helps in any ways.
I can't find where Gluster is used in their files outside of a mention in the readme so probably not. Also, the repository is using an apiVersion that does not work with the current version of Kubernetes.
Adding explanation for future reference if someone wants to check on kadalu.io
I can't find where Gluster is used in their files outside of a mention in the readme.
Gluster is used as the filesystem layer in kadalu. Kadalu just takes care of management in k8s native way (using configmap, CSI, and operator).
Also, the repository is using an apiVersion that does not work with the current version of Kubernetes.
are you talking about v1beta version? or something else? - That's resolved with kadalu/kadalu#669. Which would be part of a release this week.