We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
spawnSync
it's hard to get the error from docker-compose only get [x] command [docker compose]: ${spawnReturn.error.message}
[x] command [docker compose]: ${spawnReturn.error.message}
We need more info when node failed launch.
In docker part, we use dockerode, we can also use it's ecosystem component.
dockerode
https://github.com/apocas/dockerode-compose to replace our spawnSync part
fix the runner part in docker folder from spawnSync to dockerode but helm & kubernetes also have this problem.
docker
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the problem that you are trying to solve?
it's hard to get the error from docker-compose
only get
[x] command [docker compose]: ${spawnReturn.error.message}
We need more info when node failed launch.
新功能 Feature Request
In docker part, we use
dockerode
, we can also use it's ecosystem component.https://github.com/apocas/dockerode-compose to replace our spawnSync part
可能的解法 Proposed Solution
fix the runner part in
docker
folder from spawnSync to dockerodebut helm & kubernetes also have this problem.
The text was updated successfully, but these errors were encountered: