🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Error running Solace under Kubernetes on WSL

chewymints
chewymints Member Posts: 8 ✭
in PubSub+ Event Broker #1

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 and using the Docker compose template here: 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.

Tagged:

Answers

  • chewymints
    chewymints Member Posts: 8 ✭
    #2

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

  • chewymints
    chewymints Member Posts: 8 ✭
    #3

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

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #4

    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.

  • amackenzie
    amackenzie Member, Employee Posts: 269 Solace Employee
    #5

    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?

  • [Deleted User]
    [Deleted User] Posts: 0 ✭✭
    #6

    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: https://github.com/docker/for-win/issues/5325 you may have to edit values.yaml -> storage.useStorageClass: local-storage

  • chewymints
    chewymints Member Posts: 8 ✭
    #7

    @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:

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

Categories

This Month's Leaders

This Week's Leaders