Thanks for reaching out and sharing this suggestion! In our latest updates to the Docker env files we discovered this issue, and are planning to roll out a fix for this in our upcoming release (2025.4). You can follow the issue here, for reference.
For any other folks who run into this in the interim, we have a similar solution suggested in this thread.
Cheers 