ImportErrorlibsqlite3.so.0 while deploying a cloud function - Stack Overflow

I'm trying to deply a cloud function, using python, the code works locally fine, and the cloud build job complete successfuly, however, the cloud function is not working, I get this error :

Revision 'xxxx' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable within the allocated timeout. This can happen when the container port is misconfigured or if the timeout is too short. The health check timeout can be extended. Logs for this revision might contain more information

when I look at logs, I find this:

ImportError: libsqlite3.so.0: cannot open shared object file: No such file or directory

does anyone have an idea ?

I'm trying to deply a cloud function, using python, the code works locally fine, and the cloud build job complete successfuly, however, the cloud function is not working, I get this error :

Revision 'xxxx' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable within the allocated timeout. This can happen when the container port is misconfigured or if the timeout is too short. The health check timeout can be extended. Logs for this revision might contain more information

when I look at logs, I find this:

ImportError: libsqlite3.so.0: cannot open shared object file: No such file or directory

does anyone have an idea ?

• google-cloud-platform
• google-cloud-functions
• google-cloud-run

Share Follow asked Jan 29 at 16:08 aNameaName 3,09355 gold badges4040 silver badges7070 bronze badges 1

• Your question should show the code (a minimal complete reproducible example) that doesn't work the way you expect. Without that, it's highly unlikely that you'll get good feedback on what's wrong and how to fix it. We should be able to copy what you have and run it for ourselves with the instructions you provide. – Doug Stevenson Commented Jan 29 at 17:02

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

I had the same issue and resolved it by switching the cloud function base image to google-22-full (Ubuntu 22 full).

As mentioned here, there are different stacks with different included package that can be selected when editing cloud functions.