Skip to content

MySQL

Since testcontainers-go v0.20.0

Introduction

The Testcontainers module for MySQL.

Adding this module to your project dependencies

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

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

Usage example

ctx := context.Background()

mysqlContainer, err := mysql.RunContainer(ctx,
    testcontainers.WithImage("mysql:8"),
    mysql.WithConfigFile(filepath.Join("testdata", "my_8.cnf")),
    mysql.WithDatabase("foo"),
    mysql.WithUsername("root"),
    mysql.WithPassword("password"),
    mysql.WithScripts(filepath.Join("testdata", "schema.sql")),
)
if err != nil {
    panic(err)
}

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

Module Reference

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

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

Container Options

When starting the MySQL 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 MySQL Docker image on Docker Hub.

Image

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

By default, the container will use the following Docker image:

const defaultImage = "mysql:8"

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:

// 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.

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.

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 MySQL 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

ConnectionString

This method returns the connection string to connect to the MySQL container, using the default 3306 port. It's possible to pass extra parameters to the connection string, e.g. tls=skip-verify or application_name=myapp, in a variadic way.

connectionString, err := container.ConnectionString(ctx, "tls=skip-verify")