You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a new postgres container and then attempting to snapshot the container, an error is thrown:
2024/09/23 11:23:27 🔔 Container is ready: 1eb4447734fa
sync_test.go:111: failed to snapshot container: could not execute restore command DROP DATABASE IF EXISTS "": ERROR: zero-length delimited identifier at or near """" (SQLSTATE 42601)
The database name was set using postgres.WithDatabase(<DB_NAME>) and the container uses the docker.io/postgres:16-alpine image.
Relevant log output
2024/09/23 11:23:27 🔔 Container is ready: 1eb4447734fa
sync_test.go:111: failed to snapshot container: could not execute restore command DROP DATABASE IF EXISTS "": ERROR: zero-length delimited identifier at or near """" (SQLSTATE 42601)
Additional information
No response
The text was updated successfully, but these errors were encountered:
Testcontainers version
v0.33.0
Using the latest Testcontainers version?
Yes
Host OS
MacOS
Host arch
ARM
Go version
1.22.5
Docker version
Client: Version: 26.1.3 API version: 1.45 Go version: go1.21.10 Git commit: b72abbb Built: Thu May 16 08:30:38 2024 OS/Arch: darwin/arm64 Context: orbstack Server: Docker Engine - Community Engine: Version: 26.1.4 API version: 1.45 (minimum version 1.24) Go version: go1.21.11 Git commit: de5c9cf Built: Wed Jun 5 11:29:18 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: v1.7.19 GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc: Version: 1.1.13 GitCommit: 58aa9203c123022138b22cf96540c284876a7910 docker-init: Version: 0.19.0 GitCommit: de40ad0
Docker info
What happened?
When running a new postgres container and then attempting to snapshot the container, an error is thrown:
The database name was set using
postgres.WithDatabase(<DB_NAME>)
and the container uses thedocker.io/postgres:16-alpine
image.Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: