System Information:
OS: macOS Catalina 10.15.7
Docker Image: mcr.microsoft.com/mssql/server:2019-latest
Context:
I’m trying to get my virtual environment running again after a recent docker update and there seems to be some changes where the mssql images are being pulled from. So, I (changed) my docker file FROM microsoft/mssql-server-linux:2017-latest (used to work) to... FROM mcr.microsoft.com/mssql/server:2017-latest as was required.
**With that... I was able to get the build to continue (however) I'm stuck on this terminal message "Client Storage Purge" :**cfml_1 | WARNING: org.xerial's sqlite-jdbc is not loaded. cfml_1 | Please provide the jar on your classpath to parse sqlite files. cfml_1 | See tika-parsers/pom.xml for the correct version. database_1 | 2021-07-19 21:34:50.58 spid51 Using 'dbghelp.dll' version '4.0.5' 2021-07-19 21:36:32.70 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 2021-07-19 21:36:32.79 spid51 Using 'xplog70.dll' version '2017.140.3401' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. cfml_1 | [INFO ] runwar.context: Jul 19, 2021 22:38:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 19, 2021 23:45:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 00:52:43 AM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 02:26:11 AM Information [scheduler-2] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 05:47:17 AM Information [scheduler-1] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 10:59:59 AM Information [scheduler-0] - Run Client Storage Purge
Questions:
Why is there such a long delay?
How can we fix it to get this build to finish?
Is this an issue with the docker image or the JDBC driver?
My issue turned out to be due to a problem with the coldfusion version I was using in my docker build and not "sqlite-jdbc". With that said I'm closing this issue as it's unrelated .
System Information: OS: macOS Catalina 10.15.7 Docker Image: mcr.microsoft.com/mssql/server:2019-latest
Context: I’m trying to get my virtual environment running again after a recent docker update and there seems to be some changes where the mssql images are being pulled from. So, I (changed) my docker file FROM microsoft/mssql-server-linux:2017-latest (used to work) to... FROM mcr.microsoft.com/mssql/server:2017-latest as was required.
**With that... I was able to get the build to continue (however) I'm stuck on this terminal message "Client Storage Purge" :**
cfml_1 | WARNING: org.xerial's sqlite-jdbc is not loaded. cfml_1 | Please provide the jar on your classpath to parse sqlite files. cfml_1 | See tika-parsers/pom.xml for the correct version. database_1 | 2021-07-19 21:34:50.58 spid51 Using 'dbghelp.dll' version '4.0.5' 2021-07-19 21:36:32.70 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required. 2021-07-19 21:36:32.79 spid51 Using 'xplog70.dll' version '2017.140.3401' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required. cfml_1 | [INFO ] runwar.context: Jul 19, 2021 22:38:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 19, 2021 23:45:43 PM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 00:52:43 AM Information [scheduler-0] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 02:26:11 AM Information [scheduler-2] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 05:47:17 AM Information [scheduler-1] - Run Client Storage Purge cfml_1 | [INFO ] runwar.context: Jul 20, 2021 10:59:59 AM Information [scheduler-0] - Run Client Storage Purge
Questions:
Others seem to be having the issue ~ See reference here: microsoft/mssql-docker#554 NOTE: I also posted this same issue on Microsoft Container Registry ~ here: https://github.com/microsoft/containerregistry/issues/71 ~ as well as the microsoft /mssql-docker repository ~ here: https://github.com/microsoft/mssql-docker/issues/703
Any feedback or insight is welcome as I'm stuck in the water until I can get the dev environment working again.