Skip to content

MariaDB

Since testcontainers-go v0.24.0

Introduction

The Testcontainers module for MariaDB.

Adding this module to your project dependencies

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

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

Usage example

ctx := context.Background()

mariadbContainer, err := mariadb.RunContainer(ctx,
    testcontainers.WithImage("mariadb:11.0.3"),
    mariadb.WithConfigFile(filepath.Join("testdata", "my.cnf")),
    mariadb.WithScripts(filepath.Join("testdata", "schema.sql")),
    mariadb.WithDatabase("foo"),
    mariadb.WithUsername("root"),
    mariadb.WithPassword(""),
)
if err != nil {
    panic(err)
}

// Clean up the container
defer func() {
    if err := mariadbContainer.Terminate(ctx); err != nil {
        panic(err)
    }
}()

Module reference

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

func RunContainer(ctx context.Context, opts ...testcontainers.ContainerCustomizer) (*MariaDBContainer, error)
  • context.Context, the Go context.
  • testcontainers.ContainerCustomizer, a variadic argument for passing options.

Container Options

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

Tip

You can find all the available configuration and environment variables for the MariaDB Docker image on Docker Hub.

Image

If you need to set a different MariaDB Docker image, you can use testcontainers.WithImage with a valid Docker image for MariaDB. E.g. testcontainers.WithImage("mariadb:11.0.3").

Info

From MariaDB docs:

From tag 10.2.38, 10.3.29, 10.4.19, 10.5.10 onwards, and all 10.6 and later tags, the MARIADB_* equivalent variables are provided. MARIADB_* variants will always be used in preference to MYSQL_* variants.

The MariaDB module will take all the environment variables that start with MARIADB_ and duplicate them with the MYSQL_ prefix.

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 operations: ImageSubstitutor, and a No-operation implementation to be used as reference for custom implementations:

package testcontainers

import (
    "context"
    "errors"
    "fmt"
    "sync"

    "github.com/testcontainers/testcontainers-go/internal/testcontainersdocker"
    "github.com/testcontainers/testcontainers-go/internal/testcontainerssession"
)

var (
    reuseContainerMx  sync.Mutex
    ErrReuseEmptyName = errors.New("with reuse option a container name mustn't be empty")
)

// GenericContainerRequest represents parameters to a generic container
type GenericContainerRequest struct {
    ContainerRequest              // embedded request for provider
    Started          bool         // whether to auto-start the container
    ProviderType     ProviderType // which provider to use, Docker if empty
    Logger           Logging      // provide a container specific Logging - use default global logger if empty
    Reuse            bool         // reuse an existing container if it exists or create a new one. a container name mustn't be empty
}

// GenericNetworkRequest represents parameters to a generic network
type GenericNetworkRequest struct {
    NetworkRequest              // embedded request for provider
    ProviderType   ProviderType // which provider to use, Docker if empty
}

// GenericNetwork creates a generic network with parameters
func GenericNetwork(ctx context.Context, req GenericNetworkRequest) (Network, error) {
    provider, err := req.ProviderType.GetProvider()
    if err != nil {
        return nil, err
    }
    network, err := provider.CreateNetwork(ctx, req.NetworkRequest)
    if err != nil {
        return nil, fmt.Errorf("%w: failed to create network", err)
    }

    return network, nil
}

// GenericContainer creates a generic container with parameters
func GenericContainer(ctx context.Context, req GenericContainerRequest) (Container, error) {
    if req.Reuse && req.Name == "" {
        return nil, ErrReuseEmptyName
    }

    logging := req.Logger
    if logging == nil {
        logging = Logger
    }
    provider, err := req.ProviderType.GetProvider(WithLogger(logging))
    if err != nil {
        return nil, err
    }
    defer provider.Close()

    var c Container
    if req.Reuse {
        // we must protect the reusability of the container in the case it's invoked
        // in a parallel execution, via ParallelContainers or t.Parallel()
        reuseContainerMx.Lock()
        defer reuseContainerMx.Unlock()

        c, err = provider.ReuseOrCreateContainer(ctx, req.ContainerRequest)
    } else {
        c, err = provider.CreateContainer(ctx, req.ContainerRequest)
    }
    if err != nil {
        return nil, fmt.Errorf("%w: failed to create container", err)
    }

    if req.Started && !c.IsRunning() {
        if err := c.Start(ctx); err != nil {
            return c, fmt.Errorf("%w: failed to start container", err)
        }
    }
    return c, nil
}

// GenericProvider represents an abstraction for container and network providers
type GenericProvider interface {
    ContainerProvider
    NetworkProvider
    ImageProvider
}

// GenericLabels returns a map of labels that can be used to identify containers created by this library
func GenericLabels() map[string]string {
    return testcontainersdocker.DefaultLabels(testcontainerssession.SessionID())
}

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.

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 one single method: AsCommand(), which returns a slice of strings 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 started.

WithNetwork

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

By default, the container is started in the default Docker network. If you want to use a different Docker network, you can use the WithNetwork(networkName string, alias string) option, which receives the new network name and an alias as parameters, creating the new network, attaching the container to it, and setting the network alias for that network.

If the network already exists, Testcontainers for Go won't create a new one, but it will attach the container to it and set the network alias.

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.

Set username, password and database name

If you need to set a different database, and its credentials, you can use WithUsername, WithPassword, WithDatabase options.

Info

The default values for the username is root, for password is test and for the default database name is test.

Init Scripts

If you would like to perform DDL or DML operations in the MariaDB container, add one or more *.sql, *.sql.gz, or *.sh scripts to the container request, using the WithScripts(scriptPaths ...string). Those files will be copied under /docker-entrypoint-initdb.d.

CREATE TABLE IF NOT EXISTS profile (
    id MEDIUMINT NOT NULL AUTO_INCREMENT,
    name VARCHAR(30) NOT NULL,
    PRIMARY KEY (id)
);

INSERT INTO profile (name) values ('profile 1');

Custom configuration

If you need to set a custom configuration, you can use WithConfigFile option to pass the path to a custom configuration file.

Container Methods

The MariaDB container exposes the following methods:

ConnectionString

This method returns the connection string to connect to the MariaDB container, using the default 3306 port. It's possible to pass extra parameters to the connection string, e.g. tls=false, in a variadic way.

Info

By default, MariaDB transmits data between the server and clients without encrypting it.

// By default, MariaDB transmits data between the server and clients without encrypting it.
connectionString, err := container.ConnectionString(ctx, "tls=false")