Comment From: quaff
Db2R2dbcDockerComposeConnectionDetailsFactory removed since com.ibm.db2:db2-r2dbc is not an actual driver.
Unable to create a ConnectionFactory for 'ConnectionFactoryOptions{options={database=testdb, host=127.0.0.1, driver=db2, password=REDACTED, port=50000, user=db2inst1}}'. Available drivers: [ oracle, sqlserver, postgresql ]
java.lang.IllegalStateException: Unable to create a ConnectionFactory for 'ConnectionFactoryOptions{options={database=testdb, host=127.0.0.1, driver=db2, password=REDACTED, port=50000, user=db2inst1}}'. Available drivers: [ oracle, sqlserver, postgresql ]
at io.r2dbc.spi.ConnectionFactories.get(ConnectionFactories.java:143)
Comment From: quaff
Need more disk space to run tests.
Comment From: wilkinsona
I've force-pushed this having rebased it on the latest main. That should mean the PR picks up some recent changes to the runner preparation that will make more free disk space available.
Comment From: wilkinsona
This is blocked until the questions regarding the licence acceptance have been resolved.
Comment From: philwebb
I looks like DB2 is also being removed from Docker Hub (see https://community.ibm.com/community/user/datamanagement/blogs/vijaya-katikireddy/2023/02/04/db2-community). Given that and the license issues, I'm not sure that we should try to support this.
Comment From: quaff
I looks like DB2 is also being removed from Docker Hub (see https://community.ibm.com/community/user/datamanagement/blogs/vijaya-katikireddy/2023/02/04/db2-community). Given that and the license issues, I'm not sure that we should try to support this.
This PR use new icr.io/db2_community/db2 for test.
Comment From: wilkinsona
I believe that this is the relevant license.
It contains the following usage restriction:
1. Usage Restrictions
(a) The Program may use a maximum of 4 processor cores and 16 GB of memory on each physical or virtual server.
I think we could comply with the license by setting some CPU and memory limits in the compose files used for testing. Whether or not it's worth the trouble is another question.
Comment From: philwebb
I think unfortunately the usage restrictions, combined with the fact that the image isn't in Docker Hub means we probably shouldn't add support for this. Thanks anyway for the PR @quaff!