# Error running Solace under Kubernetes on WSL

**URL:** <https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171>\
**Category:** Solace Event Broker\
**Tags:** docker, kubernetes\
**Created:** [February 1, 2020, 8:59am UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171 "2020-02-01T08:59:49Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![chewymints](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chewymints](https://community.solace.com/u/chewymints)\
**Post date:** [February 1, 2020, 8:59am UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/1 "2020-02-01T08:59:49Z")

</div>

Hello,  
I have been struggling to get Solace running under k8s on WSL.  
I have tried using the Helm templates here: [https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart](https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart) and using the Docker compose template here: [https://github.com/SolaceLabs/solace-single-docker-compose](https://github.com/SolaceLabs/solace-single-docker-compose)

In both cases the container stops with the Unable to raise event; rc(would block) error. I have tried all sorts of things but nothing seems to work.

Using the Docker compose template, the container runs without any problems.

---

<div class="post-metadata">

**Author:** ![chewymints](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chewymints](https://community.solace.com/u/chewymints)\
**Post date:** [February 3, 2020, 3:04am UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/2 "2020-02-03T03:04:57Z")

</div>

I have to report some progress - it works if the storage:persistent value is set to false in the helm template.

---

<div class="post-metadata">

**Author:** ![chewymints](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chewymints](https://community.solace.com/u/chewymints)\
**Post date:** [February 11, 2020, 12:27am UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/3 "2020-02-11T00:27:54Z")

</div>

@TomF : I was hoping someone from Solace could give me some insight into this.

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [February 19, 2020, 3:42pm UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/4 "2020-02-19T15:42:05Z")

</div>

Hi @chewymints k8s isn’t really my area of expertise which is why I’ve refrained from commenting. Let me see if someone can help.

---

<div class="post-metadata">

**Author:** ![amackenzie](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/amackenzie/32/1168_2.png) [@amackenzie](https://community.solace.com/u/amackenzie)\
**Post date:** [February 19, 2020, 3:51pm UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/5 "2020-02-19T15:51:10Z")

</div>

Hi @chewymints could we get more info on your K8S deployment? Is it Minikube running on WSL? Do you have a storage provider? If so which one?  
Which version of WSL are you using? Which distro? Is it required that you must make this work in WSL or could you use a VM?

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/solace/original/1X/1248f38eea018157e66cc024e8284f3331a54f94.png) [@system](https://community.solace.com/u/system)\
**Post date:** [February 19, 2020, 4:18pm UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/6 "2020-02-19T16:18:24Z")

</div>

Can you please provide the output of “kubectl get storageclass”. Unless you set storage.useStorageClass in your values.yaml file we will be using the storage class marked as “default” . Looking at this: [Kubernetes Volumes not correctly mounted with WSL2 · Issue #5325 · docker/for-win · GitHub](https://github.com/docker/for-win/issues/5325) you may have to edit values.yaml → storage.useStorageClass: local-storage

---

<div class="post-metadata">

**Author:** ![chewymints](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chewymints](https://community.solace.com/u/chewymints)\
**Post date:** [February 27, 2020, 10:22pm UTC](https://community.solace.com/t/error-running-solace-under-kubernetes-on-wsl/171/7 "2020-02-27T22:22:07Z")

</div>

@amackenzie  
Apologies for the delayed response. I have just managed to get back to this.  
The k8s deployment is a test deployment for now. I am playing around with Solace and k8s to see what is possible. For now, it’s just Docker Desktop with k8s enabled and managed using CLI on WSL. I have also verified that the error happens without WSL enabled as well.

@KenBarr  
The output is below:

```auto
kubectl get storageclass
NAME PROVISIONER AGE
hostpath (default) docker.io/hostpath 24h

```
