Running Testcontainers via Maven works on remote, doesn't work on local

[pmarshall111]

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:

(base) peter@chronos:~$ docker container ls -a
CONTAINER ID   IMAGE                       COMMAND                  CREATED          STATUS                      PORTS                                         NAMES
4446b6c07085   mariadb:10.5.5              "docker-entrypoint.s…"   45 seconds ago   Exited (1) 43 seconds ago                                                 reverent_swanson
f7ed76708cc1   testcontainers/ryuk:0.3.3   "/app"                   46 seconds ago   Up 44 seconds               0.0.0.0:49209->8080/tcp, :::49209->8080/tcp   testcontainers-ryuk-54919aaf-3158-403a-8d23-b8c4428c9ea8

(base) peter@chronos:~$ docker logs 4446b6c07085
2022-02-22 13:01:14+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.5+maria~focal started.
2022-02-22 13:01:14+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-02-22 13:01:14+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.5+maria~focal started.
2022-02-22 13:01:14+00:00 [ERROR] [Entrypoint]: mysqld failed while attempting to check config
	command was: mysqld --verbose --help --log-bin-index=/tmp/tmp.X2haDsoyha
	mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 13 "Permission denied")
Fatal error in defaults handling. Program aborted

Permissions of /etc/mysql/conf.d: (Should be readable to everyone)

(base) peter@chronos:/etc/mysql$ ls -l
total 24
drwxr-xr-x 2 root root 4096 Jul 31  2020 conf.d
(base) peter@chronos:/etc/mysql/conf.d$ ls -l
total 8
-rw-r--r-- 1 root root  8 Aug  3  2016 mysql.cnf
-rw-r--r-- 1 root root 55 Aug  3  2016 mysqldump.cnf

Here's the output from docker when running from IntelliJ:

(base) peter@chronos:~$ docker container ls -a
CONTAINER ID   IMAGE                       COMMAND                  CREATED         STATUS         PORTS                                         NAMES
50376d3e3fcf   mariadb:10.5.5              "docker-entrypoint.s…"   3 seconds ago   Up 2 seconds   0.0.0.0:49216->3306/tcp, :::49216->3306/tcp   zen_meninsky
3d50d6ddb81d   testcontainers/ryuk:0.3.3   "/app"                   4 seconds ago   Up 3 seconds   0.0.0.0:49215->8080/tcp, :::49215->8080/tcp   testcontainers-ryuk-c780ab9f-8e5b-480c-bdb9-e0c1e62ab009
(base) peter@chronos:~$ docker logs 50376d3e3fcf
2022-02-22 13:06:32+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.5+maria~focal started.
2022-02-22 13:06:32+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-02-22 13:06:32+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.5+maria~focal started.
2022-02-22 13:06:32+00:00 [Note] [Entrypoint]: Initializing database files

^ The logs then continue as expected.

Here's the output of the maven command:

[INFO] --- maven-failsafe-plugin:3.0.0-M5:integration-test (default-cli) @ Football ---
[INFO] 
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running database.WriteIT
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 361.742 s <<< FAILURE! - in database.WriteIT
[ERROR] database.WriteIT  Time elapsed: 361.742 s  <<< ERROR!
org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
Caused by: java.lang.IllegalStateException: Container exited with code 1

This is the class I'm trying to run:

public class WriteIT {
    @Container
    public static final MariaDBContainer mariaDb = new MariaDBContainer<>(DockerImageName.parse("mariadb:10.5.5"));

    public static GenerateData data;

    @BeforeAll
    public static void setup() {
        mariaDb.start();
        DS_Main.openTestConnection(
                mariaDb.getJdbcUrl(),
                mariaDb.getUsername(),
                mariaDb.getPassword()
        );
        DS_Main.initDB();
        data = addBulkData(true);
    }

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!

[kiview]

This is a long shot, but I see this (base) in your shell (indicating an active pipenv environment?). Not sure if pipenv maps the uid or something?

Also, does it work if you run mvn from the terminal within IntelliJ?

[pmarshall111]

It's the same when calling from a normal shell unfortunately, both from within the Linux terminal and within IntelliJ's terminal.

Thanks for the idea though, I appreciate this probably isn't a testcontainers issue.

[pmarshall111]

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:

   @Container
    public static final MariaDBContainer mariaDb = new MariaDBContainer<>(DockerImageName.parse("mariadb:10.5.5")).withPrivilegedMode(true);

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