[BUG] mailman-core container changed ip address, LMTP files weren't regenerated

Tag/version of Container Images
Choose from: 0.5

When doing some reconfiguration, I had to rerun docker compose up and for some reason it seems the mailman-core container received a different IP address.
First the container seems to have had 172.19.199.5 which was set up in /opt/mailman/core/var/data/postfix_lmtp.
However when checking the docker network it turned out that the container received 172.19.199.3.
As a quick workaround I quickly set the IP addresses of all three containers directly in the docker-compose.yml. But I am wondering whether there is some issue with the logic which determines whether the lmtp file needs to be regenerated: https://github.com/maxking/docker-mailman/blob/6b091fc17a578437b320c9ae85bfe50d1a616aef/core/docker-entrypoint.sh#L263

Maybe the implementation in mailman needs some tweaking to work in a container?

Start with core/docker-entrypoint.sh around line 263 and inspect how the LMTP file at /opt/mailman/core/var/data/postfix_lmtp is regenerated. Compare that logic with the container networking described in docker-compose.yml and verify behavior after the mailman-core container receives a new IP. Done means the issue is reproduced, the regeneration decision is corrected or explained, and the relevant container setup is validated.