Java Containers for Popular Databases

[elaine-jackson]

I am working on a pull request to add support for Java 11 + MariaDB (see: #1285). I would like to take the initiative to support other database configurations if allowed. This would create several pull requests and add a lot more container options (are we trying to keep this project small?). This would make GitHub Codespaces and VS Code Dev Containers much more useful to my workflow. This issue can also be used as a checklist on the progress.

I would like to add Java containers for the following database configurations:

• Java with MySQL (https://hub.docker.com/_/mysql): Differences between MariaDB and MySQL are subtle but they are two different databases each deserving of its own configuration.
• Java with Elasticsearch (https://hub.docker.com/_/elasticsearch)
• Java with Redis (https://hub.docker.com/_/redis)
• Java with PostgreSQL (https://hub.docker.com/_/postgres)
• Java with Apache Cassandra (https://hub.docker.com/_/cassandra)
• Java with MongoDB (https://hub.docker.com/_/mongo)
• Java with Couchbase (https://hub.docker.com/_/couchbase)

Maintainers: These databases are specific to certain cloud providers. I'm willing to do these if they are in scope:

• Java with DynamoDB-Local (https://hub.docker.com/r/amazon/dynamodb-local)

Maintainers: These are closed source databases, what are the licensing rules? Can we consider a merge request for these?

• Java with MS SQL (Express?) (https://hub.docker.com/_/microsoft-mssql-server)
• Java with Oracle DB (https://hub.docker.com/_/oracle-database-enterprise-edition)
• Java with IBM® Db2® Database (https://hub.docker.com/r/ibmcom/db2)

Would this series of pull requests be acceptable? If yes, should I only focus on Java 11 or also add containers for Java 8 and Java 17. Which version of the databases should we use? The newest LTS or create containers each version?

Relates to: Codespaces and Remote Containers