[Bug]: [MariaDB] getLivenessCheckPortNumbers incorrectly implemented

[AB-xdev]

Module

MariaDB

Testcontainers version

1.21.1

Problem at least present since 1.16.0

Using the latest Testcontainers version?

Yes

What happened?

testcontainers-java/modules/mariadb/src/main/java/org/testcontainers/containers/MariaDBContainer.java

Lines 64 to 66 in 7d83019

	public Set<Integer> getLivenessCheckPortNumbers() {
	return Sets.newHashSet(MARIADB_PORT);
	}

The MAPPED port is NOT returned, which causes the HostPortWaitStrategy to fail.

Why does this method exists in the first place? I couldn't find why it even exists. The super Method should work just fine.

Additional Information

This is part of a general performance regression in JDBC containers (waitUntilContainerStarted), that I'm currently addressing. I will create some follow up issues too describe the problem/s in more detail soon.

[PreAgile]

I'd like to work on this. The fix is straightforward — delegate to super.getLivenessCheckPortNumbers() instead of returning the hardcoded internal port. This matches the fix applied to other containers in PR #5734.

I've updated both MariaDBContainer implementations and added a test.

PR: #11577