Question : taking advantage of docker caching while building MySqlContainter.

[bhchandra]

Issue:
I am having a little difficulty in figuring out how to take advantage of docker-caching to improve the speed of using test-containers.

Here is my simple use-case. When executing a test which uses MySQLContainer provided by TestContainers:

1. The container boots up and executes the init script init_mysql.sql every time for setting up database schema. This step can be cached.

MySQLContainer mySQLContainer = new MySQLContainer()
                .withDatabaseName("test_database")
                .withInitScript("mysql-container/init_mysql.sql")
                .withUsername("test")
                .withPassword("test")
                .start();

2. After the init script is executed and the container is ready, a java.sql.connection is created to the database and some of the tables are populated with data. This step can also be cached, by somehow included it during the creation of docker image.

All of this takes more ~1m30sec to 2m for the container to be ready for testing.

Question:
How can above code/process be restructured so that it can advantage of docker-caching feature to enable faster testing time ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[bhchandra]

unstale

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.