[Bug]: Encountered error: "MySQL server does not support required protocol 41+" when connecting with MySQL 8.0

[anhtranbk]

Testcontainers version

0.32.0

Using the latest Testcontainers version?

Yes

Host OS

Mac OS

Host arch

Arm64

Go version

1.22

Docker version

Client:
 Version:           27.0.3
 API version:       1.46
 Go version:        go1.21.11
 Git commit:        7d4bcd8
 Built:             Fri Jun 28 23:59:41 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.32.0 (157355)
 Engine:
  Version:          27.0.3
  API version:      1.46 (minimum version 1.24)
  Go version:       go1.21.11
  Git commit:       662f78c
  Built:            Sat Jun 29 00:02:44 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.18
  GitCommit:        ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc:
  Version:          1.7.18
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Docker info

Client:
 Version:    27.0.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.15.1-desktop.1
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.28.1-desktop.1
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.32
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.10.0
    Path:     /Users/anh.tran6/.docker/cli-plugins/docker-scout

Server:
 Containers: 19
  Running: 1
  Paused: 0
  Stopped: 18
 Images: 16
 Server Version: 27.0.3
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.32-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 7.755GiB
 Name: docker-desktop
 ID: daea4b5f-1fa2-4b68-bc6a-0dad08053891
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/anh.tran6/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

What happened?

Hello,
I’m not sure if this is a bug, but I have tried many ways to fix it without success.
When writing tests to connect with MySQL using testcontainers, I occasionally encounter a rather strange error as follows:

[error] failed to initialize database, got error MySQL server does not support required protocol 41+
--- FAIL: Test_getAllPromotions/when_get_ongoing_promotions_without_cache (0.01s)
--- FAIL: Test_getAllPromotions (14.31s)
panic: MySQL server does not support required protocol 41+ [recovered]
        panic: MySQL server does not support required protocol 41+

Initially, I thought that the MySQL container might need some time to start up and wasn’t ready to connect yet, so in addition to using wait strategies, I paused my tests for a bit. However, this issue still occurred.

The puzzling thing is that once this error happens, even if I wait a few more seconds and try to reconnect, the error continues to occur. The only thing I can do is rerun my tests. This error makes my tests very flaky and quite annoying.

Here is my code snippet for initializing the MySQL container:

func MustInitMySQLContainer(t *testing.T, cfg *config.Config) *mysql.MySQLContainer {
	ctx := context.Background()
	mysqlContainer, err := mysql.Run(ctx, "mysql:8.0",
		testcontainers.WithEnv(map[string]string{
			"MYSQL_ROOT_PASSWORD": cfg.MySQL.Password,
			"MYSQL_DATABASE":      cfg.MySQL.Database,
			"MYSQL_USER":          cfg.MySQL.Username,
			"MYSQL_PASSWORD":      cfg.MySQL.Password,
		}),
		testcontainers.WithWaitStrategy(
			wait.ForLog("port: 3306  MySQL Community Server - GPL").WithStartupTimeout(30*time.Second),
			wait.ForListeningPort("3306/tcp"),
		),
	)
	if err != nil {
		t.Fatalf("failed to start container: %s", err)
	}
	return mysqlContainer
}

Relevant log output

No response

Additional information

No response

[mdelapenya]

Thanks for the issue report. Do you think this could be related? golang/go#49134

[mdelapenya]

@anhtranbk could you check if this issue can be closed? I feel it does not come from testcontainers code itself.

[sugawani]

@anhtranbk
I think this is MySQL8.0 & go-mysql-driver issue.
This error is related to authentication and can be resolved by setting sql.Open AllowNativePassword: true.
Cloud you try it?

[mdelapenya]

As per @sugawani comment, I think we can close this one. Thanks all for your contribution!