Browse Source
The new image is configured as compatible with the old image, which it actually isn't. The default database names are different, so we also set a database name that is different both from the one used by TestContainers as default and the one used by the Docker image. If the TestContainers default is used the database is not found, because the image just creates the default one and the name doesn't mach. If the Docker image default is used, the image creates its default database and then tries to create it again, which fails. These workarounds may be removed once TestContainers properly supports the new image. Closing #1528pull/1543/head
2 changed files with 7 additions and 2 deletions
Loading…
Reference in new issue