All nodes will CrashLoopBackOff on local Kubernetes

Hi, I am facing a problem during setting up memsql cluster on Kubernetes with Installation guides.
Environment is Docker desktop for Mac 2.1.0.5 and I specified hostpath as storageClass for memsql-cluster.yaml.
After executing kubectl create -f memsql-cluster.yaml command, aggregator, master and all leaves fall into CrashLoopBackOff with following log messages.

~/.docker/Volumes/pv-storage-node-memsql-cluster-master-0/pvc-ca2c04df-3829-11ea-87a5-025000000001/instance/tracelogs/memsql.log
2109 2020-01-16 06:48:33.562 INFO: Log opened
01723299 2020-01-16 06:48:35.283   INFO: Initializing OpenSSL
01724863 2020-01-16 06:48:35.285   INFO: MemSQL version hash: 09a41c2d993fc5dcf31c70a8b8989caaf8b329fd (Sat Dec 7 01:00:24 2019 -0500)
02028688 2020-01-16 06:48:35.589   INFO: Couldn't increase GC thread scheduling priority. Continuing at normal priority
02028760 2020-01-16 06:48:35.589   INFO: Couldn't increase GC thread scheduling priority. Continuing at normal priority
02034701 2020-01-16 06:48:35.595  ERROR: Can't start server: Bind on UNIX socket (36)
02035339 2020-01-16 06:48:35.595  ERROR: Do you already have another memsqld server running on socket: memsql.sock ?
02035842 2020-01-16 06:48:35.596  ERROR: Failed to start MemSQL
02036294 2020-01-16 06:48:35.596  ERROR: ./memsqld: exiting

It seems that there is no another memsql.sock file during starting memsqld.
Do you have an idea about the cause and how to fix this problem?

Thank you in advance for your help.