Vincent van Dam

If you would like to achieve this, I think the best approach would be a solution in the dsk image itself (eg a smart bootloader in the root sector).

In earlier versions kubedock was using deployments, and had the option to use jobs. Deployments were problematic when the orchestrated containers were actually one-off jobs (jobs did solve that). A...

With the TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX environment set, testcontainers-node tries to lock itself twice. Since it had locked itself already, the second lock attempt fails (and the timeout occurs). Not sure, why this...

It fails because of this constant: https://github.com/testcontainers/testcontainers-node/blob/v10.8.1/packages/testcontainers/src/reaper/reaper.ts#L9 Being compared with a rewritten image: https://github.com/testcontainers/testcontainers-node/blob/v10.8.1/packages/testcontainers/src/generic-container/generic-container.ts#L70 This is a bug in testcontainers-node. Workarounds are: * TESTCONTAINERS_RYUK_DISABLED=true * RYUK_CONTAINER_IMAGE="${TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX}/testcontainers/ryuk:0.5.1" (edited)

Yes, that makes sense and would be much appreciated.

I am trying to reproduce as well (using minikube), but I can't. Both with and without the --pre-archive all tests produce the expected output. Is the instance of kubedock able...

Did some more extensive testing and the only way to reproduce is when the volumes which are to be bound, are not directly accessible by kubedock. The other working methods...

@mausch @jonesbusy I added support for mounts in hostconfig, that fixed ryuk support for dotnet at my end.

It's not supported at the moment. Do you have a small project that can be used for testing this?

Definitely makes sense to return a different error code based on the signal. Do you know if there is a standardized mapping I can follow? This is where the ezit...