Running Testcontainers via Maven works on remote, doesn't work on local #5112
Replies: 2 comments 1 reply
-
This is a long shot, but I see this Also, does it work if you run |
Beta Was this translation helpful? Give feedback.
-
It looks like a potential fix could be to run the container in privileged mode: https://blog.birost.com/a?ID=01750-3aba89d5-cc3f-4fd3-9bc4-5f34d2365dfc However, changing the container to privileged mode doesn't help in this instance:
If anyone has any further ideas I'd love to hear them. For now though, I'm giving up on this and will just run the tests via IntelliJ |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, I have a project set up using testcontainers.
Everything works fine when I right click "Run tests" in IntelliJ, and everything works fine on GitHub Actions using the command "mvn clean test verify", but when I try to run "mvn clean test verify" locally, my mariadb container starts and then dies instantly
Does anyone have any ideas/leads?
Here's the output from docker when running the command from maven:
Permissions of /etc/mysql/conf.d: (Should be readable to everyone)
Here's the output from docker when running from IntelliJ:
^ The logs then continue as expected.
Here's the output of the maven command:
This is the class I'm trying to run:
Again, this all works fine on local when running via IntelliJ, but not via maven. Here's my pom.xml:
https://github.com/pmarshall111/Football-Core/blob/master/pom.xml
Many thanks if anyone has any ideas!
Beta Was this translation helpful? Give feedback.
All reactions