search

ibmdb / node-ibm_db

IBM DB2 and IBM Informix bindings for node
MIT License
190 stars 151 forks source link

ibm_db Library Not Working with Docker image with Node greater than 14.17 #844

Closed jsalcedoa closed 2 years ago

jsalcedoa commented 2 years ago

Hi,

We are working on an internal project for IBM and we are having the following issue in Production, could you please help us give priority to this ticket?

We are deploying our Node Js application to a Kubernetes cluster using Docker, we were not able to deploy a small change because it fails when Kubernetes tries to create the instance of the deployment and the pod. The issue is caused due to the "ibm_db" library (see screenshot) and the version of node used in the Docker Hub image we are using.

image

Every time that the version of Node gets updated in the image used from the Docker Hub we get some type of errors with the "ibm_db" library and we were solving this issue before by using a Docker Hub image with a lower version of Node. But now the only version available lower than 14.19 is 12.22 and this one is giving us some other issues, the Node version we were using with the library with no problems was 14.17.

The new version of node in docker updated from 14.18 to 14.19 and after this update we started having this issue.

I include the link from an issue we opened time ago when we had problems with the "ibm_db" as well when the Node version of the Docker Hub image updated. We were able to solve this old issue as well by using a Docker Hub image with a lower version of Node.

https://github.com/ibmdb/node-ibm_db/issues/803

We need your help to guide us on what steps we need to do or to fix the incompatibility issue on your end because we can not use version 12 of Node but the version 14.17 or 14.18 is now longer available in Docker Hub.

Thanks Team.

jsalcedoa commented 2 years ago

No further assistance is needed is needed in this ticket I was able to resolve the issue by un installing node-sass and installing only sass package. I did several things that I can't really remember because I was troubleshooting all day. But I was also able to come to a conclusion for the ticket https://github.com/ibmdb/node-ibm_db/issues/803, I added additional notes there too.