Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start Callisto container; #12

Open
alex270795 opened this issue Jul 24, 2024 · 7 comments
Open

Unable to start Callisto container; #12

alex270795 opened this issue Jul 24, 2024 · 7 comments

Comments

@alex270795
Copy link

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
Copy link
Contributor

@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
Copy link
Author

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

@vpokotilov
Copy link
Contributor

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

@alex270795
Copy link
Author

alex270795 commented Jul 25, 2024

@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
Copy link
Contributor

@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
Copy link
Author

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

@vpokotilov
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants