Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expose TestcontainersContainer client

See original GitHub issue

Please can you expose the client in TestcontainersContainer?

I need to extend the TestcontainersContainer to add copying files from the container and I want to re-use the client instead of creating a different client.

[Edit]: How can we re-use the dockerclient in out extension method?

Please!!!

Issue Analytics

State:
Created 2 years ago
Comments:9

Top GitHub Comments

1reaction

eabacommented, Jan 31, 2022

0reactions

HofmeisterAncommented, Mar 4, 2022

I’ll close this in favor of #430.

Top Results From Across the Web

Networking and communicating with containers

Exposing container ports to the host. It is common to want to connect to a container from your test process, running on the...

Custom configuration

Used by Ryuk, Docker Compose, and a few other containers that need to perform Docker actions. Example: /var/run/docker-alt.sock. TESTCONTAINERS_HOST_OVERRIDE

Networking and communicating with containers

Then, communication can occur between networked containers without the need of exposing ports through the host. With Testcontainers, you can do this as...

Java Testcontainers - Cannot connect to exposed port

So I started to port those tests to TestContainers using my POP3 Server image as a GenericContainer and starting my POP3 Client classes...

How to specify port for container to be exposed on #1659

I misunderstood. As part testcontainer, ryuk docker container was running on port 8080. Is there a way to run/control ryuk to run on...