-
Notifications
You must be signed in to change notification settings - Fork 508
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
docker compose failed to start, csghub-server-1 is unhealthy #894
Comments
I found that the error seems to be:
But i did not run any runner-related functions. |
It seems you didn't start by release v1.2.3, It's main branch? |
Yes, I am using: https://github.com/OpenCSGs/csghub-installer/tree/main/docker-compose |
if your csghub is not configured a k8s to work with, then you can ignore below error |
@Tendo33 Please using package in release v1.2.3, It has a bug in main that we haven't fixed. |
@wayneliu0019 this error cause csghub-server cannot be started |
@Yiling-J pleas have a look |
@Tendo33 When you use the csghub-installer main branch, it installs the nightly version of CSGHub, which is built every night from the main branch of CSGHub. Please note that the main branch is under active development, and we cannot guarantee stability. To resolve the issue you encountered, please switch to the csghub-installer release branch and try again. sorry for the inconvenience and we’ll work on improving the README to clarify this. |
Describe the bug
Then I looked at the temporal container's log:
Environment
CSGHub Version: v0.7|v0.8|...
OS: Linux | Windows | MacOS..
Hardware: 2c4G | 4c8G |...
Launch: docker compose | helm chart
To Reproduce
Steps to reproduce the behavior:
The latest docker compose file, after changing the host IP in the
.env
file, executedbash startup.sh
.Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: