Generic containers


Testcontainers' generic container support offers the most flexibility, and makes it easy to use virtually any container images as temporary test dependencies. For example, if you might use it to test interactions with:

  • NoSQL databases or other data stores (e.g. redis, elasticsearch, mongo)
  • Web servers/proxies (e.g. nginx, apache)
  • Log services (e.g. logstash, kibana)
  • Other services developed by your team/organization which are already dockerized


A generic container rule can be used with any public docker image; for example:

// Set up a redis container
public static GenericContainer redis =
    new GenericContainer("redis:3.0.2")

// Set up a plain OS container and customize environment, 
//   command and exposed ports. This just listens on port 80 
//   and always returns '42'
public static GenericContainer alpine =
    new GenericContainer("alpine:3.2")
               .withEnv("MAGIC_NUMBER", "42")
               .withCommand("/bin/sh", "-c", 
               "while true; do echo \"$MAGIC_NUMBER\" | nc -l -p 80; done");

These containers, as @ClassRules, will be started before any tests in the class run, and will be destroyed after all tests have run.

Accessing a container from tests

The class rule provides methods for discovering how your tests can interact with the containers:

  • getContainerIpAddress() returns the IP address where the container is listening
  • getMappedPort(...) returns the Docker mapped port for a port that has been exposed on the container

For example, with the Redis example above, the following will allow your tests to access the Redis service:

String redisUrl = redis.getContainerIpAddress() + ":" + redis.getMappedPort(6379);

results matching ""

    No results matching ""