get container logs: "tail" parameter not valid #722
-
We're using testcontainers-node library (v10.7.2) to launch localstack (v3.2.0-pro) container in our integration tests. The localstack container starts, but it is stopped immediately afterwards. It seems the problem depends on the testcontainers-node library that is sending a not valid "tail" parameter for the GET container logs requests. These are the log retrieved from the kubedock container:
After this error, the localstack container is stopped. Is it possibile for you to avoid to include the tail parameter if it is not defined ? Or there is a way for me to avoid the problem ? Thanks for your support. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @sannaroby, the Docker log docs say:
I'm not familiar with kubedock but it seems it doesn't behave the same way. Perhaps a PR to change the default of This was added recently, so as a workaround version 10.6.0 should work for you. |
Beta Was this translation helpful? Give feedback.
Hi @sannaroby, the Docker log docs say:
I'm not familiar with kubedock but it seems it doesn't behave the same way. Perhaps a PR to change the default of
-1
toall
(https://github.com/NuShoSinkuPomogliTebeTvoiSankcii/testcontainers-node/blob/cb56edabcc8e686e72da4a02f05120b1f021a398/packages/testcontainers/src/container-runtime/clients/container/docker-container-client.ts#L165) would do it.This was added recently, so as a workaround version 10.6.0 should work for you.