How to use when executing all commands in a Docker container #164
-
|
Hi! RTK seems very promising. I execute all my dev commands in Docker containers (with Docker Compose), such as :
Is there a way to configure RTK so that it understands how to handle outputs ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
RTK works with Docker Compose commands — no need to install RTK inside the container. Instead of running rtk docker compose run ..., wrap your command with rtk test, rtk err, or rtk summary: Filter test output (failures only)rtk test "docker compose run --rm <CONTAINER_NAME> pdm test" Filter errors/warnings onlyrtk err "docker compose run --rm <CONTAINER_NAME> pdm test" Generic summaryrtk summary "docker compose run --rm <CONTAINER_NAME> yarn build" RTK captures stdout/stderr from the host side and applies its filters — the container runs normally, no modifications needed. I tested this with a simple Vitest setup in Docker Compose (4 tests, 1 intentional failure): Without RTK — raw docker compose run --rm node npx vitest run (~30 lines): RUN v3.2.4 /app ❯ math.test.js (4 tests | 1 failed) 6ms ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯ FAIL math.test.js > div by zero fails ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ Test Files 1 failed (1) With RTK — rtk test "docker compose run --rm node npx vitest run" (5 lines): [full output: ~/Library/Application Support/rtk/tee/1771401980_test.log] Also since v0.21.0, rtk docker compose has native support for:
Try and say if it's good. |
Beta Was this translation helpful? Give feedback.
RTK works with Docker Compose commands — no need to install RTK inside the container.
Instead of running rtk docker compose run ..., wrap your command with rtk test, rtk err, or rtk summary:
Filter test output (failures only)
rtk test "docker compose run --rm <CONTAINER_NAME> pdm test"
rtk test "docker compose run --rm <CONTAINER_NAME> yarn test"
Filter errors/warnings only
rtk err "docker compose run --rm <CONTAINER_NAME> pdm test"
Generic summary
rtk summary "docker compose run --rm <CONTAINER_NAME> yarn build"
RTK captures stdout/stderr from the host side and applies its filters — the container runs normally, no modifications needed.
I tested this with a simple Vitest setup in Docker C…