AerospikeServer.start assumes that it cannot take more than 30 seconds to start aerospike

[aniketbhatnagar]

AerospikeServer.start has a timeout of 30 seconds for aerospike docker image to start. This makes it sometimes indeterministic as the docker image may take a little more time to start. Should we remove the timeout or set a higher timeout (like 10 minutes)?

[maxkraynov]

Hi, @aniketbhatnagar! Thank you for your issue. I would like to draw your attention to the testcontainers-java project. Actually, it's full-featured test framework based on docker containers.
You easy can run aerospike with this snippet

public static GenericContainer aerosike =
            new GenericContainer("aerospike:latest")
                    .withExposedPorts(3000)
                    .withClasspathResourceMapping("aerospike.conf", "/etc/aerospike/aerospike.conf", BindMode.READ_ONLY);

We are going to close embedded-aerospike project and focus on contributing to testcontainers-java project.