-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: MySQL 8.0.28 Container Fails to Start with Testcontainers 3.8.0 #1142
Comments
Does it fail with
I can take a look at it end of next week. |
I've tested it with I'll keep an eye out for any related errors, but so far, so good. |
I just submitted #1144 which should address this issue. Note that this problem only exist for This is also the reason why this was not caught by continuous integration since the default image against which the test are run is |
@0xced Thanks for the PR. @macalbert you can work around the issue until a new version is available by adding the following line to the builder configuration:
This will create the directory upon container start. |
Testcontainers version
3.8.0
Using the latest Testcontainers version?
Yes
Host OS
Windows/Ubuntu
Host arch
x86/ARM
.NET version
8.0
Docker version
Docker info
What happened?
When attempting to start a
MySQL 8.0.28
container using Testcontainers 3.8.0, the operation fails with a Docker.DotNet.DockerApiException, indicating that the container is not running. This issue occurs during the execution of integration tests, specifically when trying to establish a connection to the MySQL container.I'm including a simplified test scenario that demonstrates the problem. The test attempts to start a
MySQL 8.0.28
container and then perform two operations: opening a database connection and executing a simple SQL script. Both tests highlight the failure to start the container, as indicated by the Docker.DotNet.DockerApiException.Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: