Update `spawnSync` to dockerode-compose #114

New issue

Open

opened 2024-12-25 22:58:14 -05:00 by kidneyweakx · 0 comments

kidneyweakx commented

2024-12-25 22:58:14 -05:00

(Migrated from github.com)

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 dockerode
but helm & kubernetes also have this problem.

### 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 dockerode but helm & kubernetes also have this problem.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

cathayddt/bdk#114

No description provided.

Rows
Columns

Update spawnSync to dockerode-compose #114

What is the problem that you are trying to solve?

新功能 Feature Request

可能的解法 Proposed Solution

Update `spawnSync` to dockerode-compose #114