[Feature]: Expose class's fetch containerInfo timeout to user.

Module

Core

Problem

Some conditions container will excute long time to expose ports , but currently only wait 5 seconds to fetch containerInfo.

Solution

Expose class’s fetch containerInfo timeout to user and with defalt value.

Benefit

We can wait more time for heavy container to started.

Alternatives

None.

Would you like to help contributing this feature?

Yes

[GOODBOY008]

@eddumelendez Thanks , it’s worked.

[eddumelendez]

Hi @GOODBOY008! thanks for sharing! the issue is related to the host mode. I use the the following code

    private Network network = Network.newNetwork();

    @Test
    public void demonstration() {

        try (
                GenericContainer<?> OB_SERVER =
                        new GenericContainer<>("oceanbase/oceanbase-ce:3.1.4")
                                .withNetwork(network)
                                .withExposedPorts(OB_SERVER_SQL_PORT, OB_SERVER_RPC_PORT)
                                .withEnv("OB_ROOT_PASSWORD", OB_SYS_PASSWORD)
                                .waitingFor(Wait.forLogMessage(".*boot success!.*", 1))
                                .withLogConsumer(new Slf4jLogConsumer(LOG));
                GenericContainer<?> LOG_PROXY =
                        new GenericContainer<>("whhe/oblogproxy:1.0.3")
                                .withNetwork(network)
                                .withExposedPorts(LOG_PROXY_PORT)
                                .withEnv("OB_SYS_USERNAME", OB_SYS_USERNAME)
                                .withEnv("OB_SYS_PASSWORD", OB_SYS_PASSWORD)
                                .waitingFor(Wait.forLogMessage(".*boot success!.*", 1))
                                .withLogConsumer(new Slf4jLogConsumer(LOG));
        ) {
            Startables.deepStart(Stream.of(OB_SERVER, LOG_PROXY)).join();
        }
    }

and it worked. is it helps? Otherwise, I think you can follow #5151 due to this is duplicated.