rickwong / captain Goto Github PK

When you start a group, it uses docker start on each container individually. When you have containers that rely on healthchecks of other containers in your compose scripts, this will result in startup errors as they do not wait.

Changing this so the group calls docker compose ___, this should be solved.

Especially Webpack configs seem like magic.

When you use container_name in the docker-compose, the grouping is broken.

Reproduction: create the following docker-compose.yml in a folder called testdocker

services:
  node-1:
    container_name: custom-node
    image: node
    command: tail -f /dev/null

  node-2:
    image: node
    command: tail -f /dev/null

Docker desktop groups them:

Captain does not:

Please let me know if you would like me to contribute a fix myself