search

wrike / callisto

Callisto is an open-source Kubernetes-native implementation of Selenium Grid.
MIT License
108 stars 15 forks source link

Unable to start Callisto container; #12

Open alex270795 opened 2 months ago

alex270795 commented 2 months ago

Hello, I have tried to start callisto-chart in minicube, but I receive the following errors when callisto container is starting: Callisto logs.txt

Could you suggest how the issue can be solved?

BR, Alex.

vpokotilov commented 2 months ago

@alex270795 hi, something is wrong with the yaml syntax

  in "/etc/callisto/browser-pod-manifest.yaml", line 17, column 7
could not find expected ':'

Try to check the syntax of this file, for example by checking the output of the helm template . command.

alex270795 commented 2 months ago

Thanks a lot! But now I receive another issue. Have ever faced this issue? Callisto pod crashes . Callisto pod crashes.txt callisto

vpokotilov commented 2 months ago

@alex270795 Сan you get the callisto pod logs? There must be something useful there.

alex270795 commented 2 months ago

@vpokotilov It's the same issue in "/etc/callisto/browser-pod-manifest.yaml", line 17, column 7 could not find expected ':' . But, I don't understand where should be added ':' . I have copied this file from your repository: image

Maybe you have changed something but don't commited to repository?

vpokotilov commented 2 months ago

@alex270795 You can view the contents of the rendered file using the helm template .command and try to find error there.
Most likely the error occurs due to changes in values.yaml.

alex270795 commented 2 months ago

@vpokotilov it's my helm template . check: helm template.txt

vpokotilov commented 2 months ago

@alex270795 At first glance, there are no errors. Did you remember to specify your custom values ​​for the helm template command?

Another way is to view the contents of the configmap with the kubectl get configmap callisto-browser-pod-configmap -o yaml.

Please try to find the error yourself. General advice - try to configure everything from scratch, making one change at a time, to understand at what point the error appears.
We use the same chart, and everything is fine for us.