Skip to content

Timed out waiting for re-connection: Containers are killed by Reaper #925

@mordv

Description

@mordv

I'm three hours in and yet to run a hello world.
Containers are killed by reaper for some reason. And also removed automatically, as there is no .withAutoRemove(false) config. So I had to record a video to see what's happening. The output is the same as in #767

2024-05-07 21:41:29 2024/05/07 19:41:29 New client connected: 192.168.65.1:37043
2024-05-07 21:41:29 2024/05/07 19:41:29 Adding {"label":{"org.testcontainers.session-id=595d104f2d9d":true}}
2024-05-07 21:41:33 2024/05/07 19:41:33 EOF
2024-05-07 21:41:33 2024/05/07 19:41:33 Client disconnected: 192.168.65.1:37043
2024-05-07 21:41:43 2024/05/07 19:41:43 Timed out waiting for re-connection
2024-05-07 21:41:43 2024/05/07 19:41:43 Removed 1 container(s), 0 network(s), 0 volume(s) 0 image(s)

Am at least able to run something using .withReuse(), but I'd like to know how to debug the thing - where do I get output from, since reaper kills itself milliseconds after printing the last message?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions