Skip to content

ScyllaDB

Since testcontainers-go v0.36.0

Introduction

The Testcontainers module for ScyllaDB, a NoSQL database fully compatible with Apache Cassandra and DynamoDB, allows you to create a ScyllaDB container for testing purposes.

Adding this module to your project dependencies

Please run the following command to add the ScyllaDB module to your Go dependencies:

go get github.com/testcontainers/testcontainers-go/modules/scylladb

Usage example

    ctx := context.Background()

    // runScyllaDBContainerWithCustomCommands {
    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithCustomCommands("--memory=1G", "--smp=2"),
    )
    // }
    defer func() {
        if err := testcontainers.TerminateContainer(scyllaContainer); err != nil {
            log.Printf("failed to terminate container: %s", err)
        }
    }()
    if err != nil {
        log.Printf("failed to start container: %s", err)
        return
    }

    state, err := scyllaContainer.State(ctx)
    if err != nil {
        log.Printf("failed to get container state: %s", err)
        return
    }

    fmt.Println(state.Running)

    connectionHost, err := scyllaContainer.NonShardAwareConnectionHost(ctx)
    if err != nil {
        log.Printf("failed to get connection host: %s", err)
        return
    }

    if err := runGoCQLExampleTest(connectionHost); err != nil {
        log.Printf("failed to run Go CQL example test: %s", err)
        return
    }

    // Output:
    // true

 ⋯

    ctx := context.Background()

    // runScyllaDBContainerWithAlternator {

    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithAlternator(),
    )
    // }
    defer func() {
        if err := testcontainers.TerminateContainer(scyllaContainer); err != nil {
            log.Printf("failed to terminate container: %s", err)
        }
    }()
    if err != nil {
        log.Printf("failed to start container: %s", err)
        return
    }

    state, err := scyllaContainer.State(ctx)
    if err != nil {
        log.Printf("failed to get container state: %s", err)
        return
    }

    fmt.Println(state.Running)

    // scyllaDbAlternatorConnectionHost {
    // the alternator port is the default port 8000
    _, err = scyllaContainer.AlternatorConnectionHost(ctx)
    // }
    if err != nil {
        log.Printf("failed to get connection host: %s", err)
        return
    }

    // Output:
    // true

 ⋯

    ctx := context.Background()

    // runScyllaDBContainerWithShardAwareness {
    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithShardAwareness(),
    )
    // }
    defer func() {
        if err := testcontainers.TerminateContainer(scyllaContainer); err != nil {
            log.Printf("failed to terminate container: %s", err)
        }
    }()
    if err != nil {
        log.Printf("failed to start container: %s", err)
        return
    }

    state, err := scyllaContainer.State(ctx)
    if err != nil {
        log.Printf("failed to get container state: %s", err)
        return
    }

    fmt.Println(state.Running)

    // scyllaDbShardAwareConnectionHost {
    connectionHost, err := scyllaContainer.ShardAwareConnectionHost(ctx)
    // }
    if err != nil {
        log.Printf("failed to get connection host: %s", err)
        return
    }

    if err := runGoCQLExampleTest(connectionHost); err != nil {
        log.Printf("failed to run Go CQL example test: %s", err)
        return
    }

    // Output:
    // true

 ⋯

    // runScyllaDBContainerWithConfig {
    ctx := context.Background()

    cfgBytes := `cluster_name: 'Amazing ScyllaDB Test'
num_tokens: 256
commitlog_sync: periodic
commitlog_sync_period_in_ms: 10000
commitlog_segment_size_in_mb: 32
schema_commitlog_segment_size_in_mb: 128
seed_provider:
  - class_name: org.apache.cassandra.locator.SimpleSeedProvider
    parameters:
      - seeds: "127.0.0.1"
listen_address: localhost
native_transport_port: 9042
native_shard_aware_transport_port: 19042
read_request_timeout_in_ms: 5000
write_request_timeout_in_ms: 2000
cas_contention_timeout_in_ms: 1000
endpoint_snitch: SimpleSnitch
rpc_address: localhost
api_port: 10000
api_address: 127.0.0.1
batch_size_warn_threshold_in_kb: 128
batch_size_fail_threshold_in_kb: 1024
partitioner: org.apache.cassandra.dht.Murmur3Partitioner
commitlog_total_space_in_mb: -1
murmur3_partitioner_ignore_msb_bits: 12
strict_is_not_null_in_views: true
maintenance_socket: ignore
enable_tablets: true
`

    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithConfig(strings.NewReader(cfgBytes)),
    )
    // }
    defer func() {
        if err := testcontainers.TerminateContainer(scyllaContainer); err != nil {
            log.Printf("failed to terminate container: %s", err)
        }
    }()
    if err != nil {
        log.Printf("failed to start container: %s", err)
        return
    }

 ⋯

    // runBaseScyllaDBContainer {
    ctx := context.Background()

    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithShardAwareness(),
    )
    defer func() {
        if err := testcontainers.TerminateContainer(scyllaContainer); err != nil {
            log.Printf("failed to terminate container: %s", err)
        }
    }()
    if err != nil {
        log.Printf("failed to start container: %s", err)
        return
    }
    // }

    state, err := scyllaContainer.State(ctx)
    if err != nil {
        log.Printf("failed to get container state: %s", err)
        return
    }

    fmt.Println(state.Running)

    // scyllaDbNonShardAwareConnectionHost {
    connectionHost, err := scyllaContainer.NonShardAwareConnectionHost(ctx)
    // }
    if err != nil {
        log.Printf("failed to get connection host: %s", err)
        return
    }

    if err := runGoCQLExampleTest(connectionHost); err != nil {
        log.Printf("failed to run Go CQL example test: %s", err)
        return
    }

    // Output:
    // true

Module Reference

Run function

The ScyllaDB module exposes one entrypoint function to create the ScyllaDB container, and this function receives three parameters:

func Run(ctx context.Context, img string, opts ...testcontainers.ContainerCustomizer) (*Container, error)
  • context.Context, the Go context.
  • string, the Docker image to use.
  • testcontainers.ContainerCustomizer, a variadic argument for passing options.

Info

By default, we add the --developer-mode=1 flag to the ScyllaDB container to disable the various checks Scylla performs. Also in scenarios in which static partitioning is not desired - like mostly-idle cluster without hard latency requirements, the --overprovisioned command-line option is recommended. This enables certain optimizations for ScyllaDB to run efficiently in an overprovisioned environment. You can change it by using the WithCustomCommand function.

Container Options

When starting the ScyllaDB container, you can pass options in a variadic way to configure it.

Image

Use the second argument in the Run function to set a valid Docker image. In example:

scylladb.Run(context.Background(), "scylladb/scylla:6.2.1")
// OR
scylladb.Run(context.Background(), "scylladb/scylla:5.6")

Image Substitutions

In more locked down / secured environments, it can be problematic to pull images from Docker Hub and run them without additional precautions.

An image name substitutor converts a Docker image name, as may be specified in code, to an alternative name. This is intended to provide a way to override image names, for example to enforce pulling of images from a private registry.

Testcontainers for Go exposes an interface to perform this operation: ImageSubstitutor, and a No-operation implementation to be used as reference for custom implementations:

// ImageSubstitutor represents a way to substitute container image names
type ImageSubstitutor interface {
    // Description returns the name of the type and a short description of how it modifies the image.
    // Useful to be printed in logs
    Description() string
    Substitute(image string) (string, error)
}

type NoopImageSubstitutor struct{}

// Description returns a description of what is expected from this Substitutor,
// which is used in logs.
func (s NoopImageSubstitutor) Description() string {
    return "NoopImageSubstitutor (noop)"
}

// Substitute returns the original image, without any change
func (s NoopImageSubstitutor) Substitute(image string) (string, error) {
    return image, nil
}

Using the WithImageSubstitutors options, you could define your own substitutions to the container images. E.g. adding a prefix to the images so that they can be pulled from a Docker registry other than Docker Hub. This is the usual mechanism for using Docker image proxies, caches, etc.

WithImageMount

Since Docker v28, it's possible to mount an image to a container, passing the source image name, the relative subpath to mount in that image, and the mount point in the target container.

This option validates that the subpath is a relative path, raising an error otherwise.

newOllamaContainer, err := tcollama.Run(
    ctx,
    "ollama/ollama:0.5.12",
    testcontainers.WithImageMount(targetImage, "root/.ollama/models/", "/root/.ollama/models/"),
)

In the code above, which mounts the directory in which Ollama models are stored, the targetImage is the name of the image containing the models (an Ollama image where the models are already pulled).

Warning

Using this option fails the creation of the container if the underlying container runtime does not support the image mount feature.

WithEnv

If you need to either pass additional environment variables to a container or override them, you can use testcontainers.WithEnv for example:

ctr, err = mymodule.Run(ctx, "docker.io/myservice:1.2.3", testcontainers.WithEnv(map[string]string{"FOO": "BAR"}))

WithExposedPorts

If you need to expose additional ports from the container, you can use testcontainers.WithExposedPorts. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithExposedPorts("8080/tcp", "9090/tcp"))

WithEntrypoint

If you need to completely replace the container's entrypoint, you can use testcontainers.WithEntrypoint. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithEntrypoint("/bin/sh", "-c", "echo hello"))

WithEntrypointArgs

If you need to append commands to the container's entrypoint, you can use testcontainers.WithEntrypointArgs. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithEntrypointArgs("echo", "hello"))

WithCmd

If you need to completely replace the container's command, you can use testcontainers.WithCmd. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithCmd("echo", "hello"))

WithCmdArgs

If you need to append commands to the container's command, you can use testcontainers.WithCmdArgs. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithCmdArgs("echo", "hello"))

WithLabels

If you need to add Docker labels to the container, you can use testcontainers.WithLabels. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithLabels(map[string]string{
        "environment": "testing",
        "project":     "myapp",
    }))

WithFiles

If you need to copy files into the container, you can use testcontainers.WithFiles. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithFiles([]testcontainers.ContainerFile{
        {
            HostFilePath:      "/path/to/local/file.txt",
            ContainerFilePath: "/container/file.txt",
            FileMode:          0o644,
        },
    }))

This option allows you to copy files from the host into the container at creation time.

WithMounts

If you need to add volume mounts to the container, you can use testcontainers.WithMounts. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithMounts([]testcontainers.ContainerMount{
        {
            Source: testcontainers.GenericVolumeMountSource{Name: "appdata"},
            Target: "/app/data",
        },
    }))

WithTmpfs

If you need to add tmpfs mounts to the container, you can use testcontainers.WithTmpfs. For example:

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithTmpfs(map[string]string{
        "/tmp": "size=100m",
        "/run": "size=100m",
    }))

WithHostPortAccess

If you need to access a port that is already running in the host, you can use testcontainers.WithHostPortAccess for example:

ctr, err = mymodule.Run(ctx, "docker.io/myservice:1.2.3", testcontainers.WithHostPortAccess(8080))

To understand more about this feature, please read the Exposing host ports to the container documentation.

WithLogConsumers

If you need to consume the logs of the container, you can use testcontainers.WithLogConsumers with a valid log consumer. An example of a log consumer is the following:

type TestLogConsumer struct {
    Msgs []string
}

func (g *TestLogConsumer) Accept(l Log) {
    g.Msgs = append(g.Msgs, string(l.Content))
}

WithLogConsumerConfig

  • Not available until the next release of testcontainers-go main

If you need to set the log consumer config for the container, you can use testcontainers.WithLogConsumerConfig. This option completely replaces the existing log consumer config, including the log consumers and the log production options.

WithLogger

If you need to either pass logger to a container, you can use testcontainers.WithLogger.

Info

Consider calling this before other "With" functions as these may generate logs.

In this example we also use the testcontainers-go log.TestLogger, which writes to the passed in testing.TB using Logf. The result is that we capture all logging from the container into the test context meaning its hidden behind go test -v and is associated with the relevant test, providing the user with useful context instead of appearing out of band.

func TestHandler(t *testing.T) {
    logger := log.TestLogger(t)
    ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", testcontainers.WithLogger(logger))
    CleanupContainer(t, ctr)
    require.NoError(t, err)
    // Do something with container.
}

Please read the Following Container Logs documentation for more information about creating log consumers.

WithAlwaysPull

  • Not available until the next release of testcontainers-go main

If you need to pull the image before starting the container, you can use testcontainers.WithAlwaysPull().

WithImagePlatform

  • Not available until the next release of testcontainers-go main

If you need to set the platform for a container, you can use testcontainers.WithImagePlatform(platform string).

LifecycleHooks

  • Not available until the next release of testcontainers-go main

If you need to set the lifecycle hooks for the container, you can use testcontainers.WithLifecycleHooks, which replaces the existing lifecycle hooks with the new ones.

You can also use testcontainers.WithAdditionalLifecycleHooks, which appends the new lifecycle hooks to the existing ones.

Wait Strategies

If you need to set a different wait strategy for the container, you can use testcontainers.WithWaitStrategy with a valid wait strategy.

Info

The default deadline for the wait strategy is 60 seconds.

At the same time, it's possible to set a wait strategy and a custom deadline with testcontainers.WithWaitStrategyAndDeadline.

Startup Commands

Testcontainers exposes the WithStartupCommand(e ...Executable) option to run arbitrary commands in the container right after it's started.

Info

To better understand how this feature works, please read the Create containers: Lifecycle Hooks documentation.

It also exports an Executable interface, defining the following methods:

  • AsCommand(), which returns a slice of strings to represent the command and positional arguments to be executed in the container;
  • Options(), which returns the slice of functional options with the Docker's ExecConfigs used to create the command in the container (the working directory, environment variables, user executing the command, etc) and the possible output format (Multiplexed).

You could use this feature to run a custom script, or to run a command that is not supported by the module right after the container is started.

Ready Commands

Testcontainers exposes the WithAfterReadyCommand(e ...Executable) option to run arbitrary commands in the container right after it's ready, which happens when the defined wait strategies have finished with success.

Info

To better understand how this feature works, please read the Create containers: Lifecycle Hooks documentation.

It leverages the Executable interface to represent the command and positional arguments to be executed in the container.

You could use this feature to run a custom script, or to run a command that is not supported by the module right after the container is ready.

Build from Dockerfile

Testcontainers exposes the testcontainers.WithDockerfile option to build a container from a Dockerfile. The functional option receives a testcontainers.FromDockerfile struct that is applied to the container request before starting the container. As a result, the container is built and started in one go.

df := testcontainers.FromDockerfile{
    Context:    ".",
    Dockerfile: "Dockerfile",
    Repo:       "testcontainers",
    Tag:        "latest",
    BuildArgs:  map[string]*string{"ARG1": nil, "ARG2": nil},
}   

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", testcontainers.WithDockerfile(df))

WithNetwork

By default, the container is started in the default Docker network. If you want to use an already existing Docker network you created in your code, you can use the network.WithNetwork(aliases []string, nw *testcontainers.DockerNetwork) option, which receives an alias as parameter and your network, attaching the container to it, and setting the network alias for that network.

In the case you need to retrieve the network name, you can simply read it from the struct's Name field. E.g. nw.Name.

Warning

This option is not checking whether the network exists or not. If you use a network that doesn't exist, the container will start in the default Docker network, as in the default behavior.

WithNetworkByName

  • Not available until the next release of testcontainers-go main

If you want to attach your containers to an already existing Docker network by its name, you can use the network.WithNetworkName(aliases []string, networkName string) option, which receives an alias as parameter and the network name, attaching the container to it, and setting the network alias for that network.

Warning

In case the network name is bridge, no aliases are set. This is because network-scoped alias is supported only for containers in user defined networks.

WithBridgeNetwork

  • Not available until the next release of testcontainers-go main

If you want to attach your containers to the bridge network, you can use the network.WithBridgeNetwork() option.

Warning

The bridge network is the default network for Docker. It's not a user defined network, so it doesn't support network-scoped aliases.

WithNewNetwork

If you want to attach your containers to a throw-away network, you can use the network.WithNewNetwork(ctx context.Context, aliases []string, opts ...network.NetworkCustomizer) option, which receives an alias as parameter, creating the new network with a random name, attaching the container to it, and setting the network alias for that network.

In the case you need to retrieve the network name, you can use the Networks(ctx) method of the Container interface, right after it's running, which returns a slice of strings with the names of the networks where the container is attached.

Docker type modifiers

If you need an advanced configuration for the container, you can leverage the following Docker type modifiers:

  • testcontainers.WithConfigModifier
  • testcontainers.WithHostConfigModifier
  • testcontainers.WithEndpointSettingsModifier

Please read the Create containers: Advanced Settings documentation for more information.

Customising the ContainerRequest

This option will merge the customized request into the module's own ContainerRequest.

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3",
    /* Other module options */
    testcontainers.CustomizeRequest(testcontainers.GenericContainerRequest{
        ContainerRequest: testcontainers.ContainerRequest{
            Cmd: []string{"-c", "log_statement=all"},
        },
    }),
)

The above example is updating the predefined command of the image, appending them to the module's command.

Info

This can't be used to replace the command, only to append options.

WithReuseByName

This option marks a container to be reused if it exists or create a new one if it doesn't. With the current implementation, the container name must be provided to identify the container to be reused.

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithReuseByName("my-container-name"),
)

Warning

Reusing a container is experimental and the API is subject to change for a more robust implementation that is not based on container names.

WithName

  • Not available until the next release of testcontainers-go main

If you need to set the name of the container, you can use the testcontainers.WithName option.

ctr, err := mymodule.Run(ctx, "docker.io/myservice:1.2.3", 
    testcontainers.WithName("my-container-name"),
)

Warning

This option is not checking whether the container name is already in use. If you use a name that is already in use, an error is returned. At the same time, we discourage using this option as it might lead to unexpected behavior, but we understand that in some cases it might be useful.

WithNoStart

  • Not available until the next release of testcontainers-go main

If you need to prevent the container from being started after creation, you can use the testcontainers.WithNoStart option.

With Database Configuration File (scylla.yaml)

In the case you have a custom config file for ScyllaDB, it's possible to copy that file into the container before it's started, using the WithConfig(r io.Reader) function.

    ctx := context.Background()

    cfgBytes := `cluster_name: 'Amazing ScyllaDB Test'
num_tokens: 256
commitlog_sync: periodic
commitlog_sync_period_in_ms: 10000
commitlog_segment_size_in_mb: 32
schema_commitlog_segment_size_in_mb: 128
seed_provider:
  - class_name: org.apache.cassandra.locator.SimpleSeedProvider
    parameters:
      - seeds: "127.0.0.1"
listen_address: localhost
native_transport_port: 9042
native_shard_aware_transport_port: 19042
read_request_timeout_in_ms: 5000
write_request_timeout_in_ms: 2000
cas_contention_timeout_in_ms: 1000
endpoint_snitch: SimpleSnitch
rpc_address: localhost
api_port: 10000
api_address: 127.0.0.1
batch_size_warn_threshold_in_kb: 128
batch_size_fail_threshold_in_kb: 1024
partitioner: org.apache.cassandra.dht.Murmur3Partitioner
commitlog_total_space_in_mb: -1
murmur3_partitioner_ignore_msb_bits: 12
strict_is_not_null_in_views: true
maintenance_socket: ignore
enable_tablets: true
`

    scyllaContainer, err := scylladb.Run(ctx,
        "scylladb/scylla:6.2",
        scylladb.WithConfig(strings.NewReader(cfgBytes)),
    )

Warning

You should provide a valid ScyllaDB configuration file as an io.Reader when using the function, otherwise the container will fail to start. The configuration file should be a valid YAML file and follows the ScyllaDB configuration file.

With Shard Awareness

If you want to test ScyllaDB with shard awareness, you can use the WithShardAwareness function. This function will configure the ScyllaDB container to use the 19042 port and ask the container to wait until the port is ready.

scyllaContainer, err := scylladb.Run(ctx,
    "scylladb/scylla:6.2",
    scylladb.WithShardAwareness(),
)

With Alternator (DynamoDB Compatible API)

If you want to test ScyllaDB with the Alternator API, you can use the WithAlternator function. This function will configure the ScyllaDB container to use the port any port you want and ask the container to wait until the port is ready. By default, you can choose the port 8000.

scyllaContainer, err := scylladb.Run(ctx,
    "scylladb/scylla:6.2",
    scylladb.WithAlternator(),
)

With Custom Commands

If you need to pass any flag to the ScyllaDB container, you can use the WithCustomCommand function. This also rewrites predefined commands like --developer-mode=1. You can check the ScyllaDB Docker Best Practices for more information.

scyllaContainer, err := scylladb.Run(ctx,
    "scylladb/scylla:6.2",
    scylladb.WithCustomCommands("--memory=1G", "--smp=2"),
)

Container Methods

The ScyllaDB container exposes the following methods:

ConnectionHost methods

There exist three methods to get the host and port of the ScyllaDB container, depending on the feature you want.

If you just want to test it with a single node and a single core, you can use the NonShardAwareConnectionHost method. However, if you're planning to use more than one core, you should use the ShardAwareConnectionHost method, which uses the shard-awareness 19042 port.

Else, if you're planning to use the Alternator API, you should use the AlternatorConnectionHost method, which uses the default port 8000.

connectionHost, err := scyllaContainer.NonShardAwareConnectionHost(ctx)

connectionHost, err := scyllaContainer.ShardAwareConnectionHost(ctx)

// the alternator port is the default port 8000
_, err = scyllaContainer.AlternatorConnectionHost(ctx)