unable to connect to mongodb using deno inside container
First of all, I want to mention that when I run
deno task preview on my local machine / laptop, it works 🎉 . No issues there. But I need to run my deno program inside a container for depolyment reasons (currently using fly.io) it fails.
I'm using the official mongodb npm client.
I use it via an import map (maybe that matters?), deno.json:
And when I try to run the code in a container I get the following error:
checklist:
- same version of deno both places
- I've tried connecting to mongodb with the deno package mongo but I get another error about the driver not supporting load balancing... so I guess it's just out of date? (6 months since last release)
- I've tried to base my image on ubuntu:latest (install deno + run) same issue 🤔5 Replies
It seems to download the dependencies just fine? 😵💫, at first I thought it didn't cache / download correctly, but that's probably not it. I can run any command inside the docker container on request! (hopefully with minimal delay)... what's going on? 🤔
Now I suspect there's something in the glue between when
npm:mongodb asks for bson, and where it searches for the package on disk?It seems like you're encountering a module resolution issue with the
mongodb npm package when running your Deno application inside a container. The error message indicates that the bson module, which is a dependency of mongodb, cannot be found.
Here are a few steps you can take to troubleshoot and potentially resolve this issue:
1. Ensure Dependencies Are Installed: When you run your application locally, Deno caches the dependencies. However, in a container, you need to ensure that the dependencies are installed. You can do this by running deno cache on your dependencies before starting your application. This will download and compile the dependencies, including bson.
2. Check Import Map: You're using an import map to import mongodb. Make sure that the import map is correctly configured in your container environment and that Deno is aware of it when running the application.
3. Permissions: Since you're running with -A, which grants all permissions, this is unlikely to be a permissions issue. However, it's worth double-checking that the container has the necessary permissions to access the network and file system.
4. Deno Version: You've mentioned that you're using the same version of Deno in both places, which is good. Make sure that the Deno version in the container is indeed the same as the one on your local machine.
5. Container File System: There might be differences in how the file system is set up in the container compared to your local environment. Ensure that the paths where Deno expects to find the modules are correctly mapped in the container.
6. Deno MongoDB Driver: You mentioned that you tried using the Deno mongo package but encountered issues with load balancing. The documentation suggests using the officialMongoDB driver with an
npm: specifier, which you are already doing. However, if you want to give the Deno driver another try, make sure to use the latest version and check if there have been any updates or fixes regarding the load balancing issue.
7. Dockerfile Configuration: If you're using a Dockerfile to build your container image, ensure that it's set up correctly to work with Deno. This includes copying over the necessary files, setting up the correct working directory, and ensuring that the entry point or command is correct.
8. Debugging: Add more logging to your application to see if there are any other issues that might be causing the problem. You can also try running the container with an interactive shell and manually executing the Deno commands to see if you can replicate the issue.
9. Network Configuration: Since you're deploying to fly.io, make sure that the network configuration allows your container to reach the MongoDB instance. Network issues could prevent your application from connecting to the database.
If you've gone through these steps and are still facing issues, you might want to consider reaching out to the Deno community or checking if there are any knownSOLVED: starting a new fresh project (basically starting everything from scratch) seems to fix the issue, something in the repo was bad (config, code... not sure), causing the app to not work in containers :deno_it_works:
The 3rd party module on
x/mongo also works well, I have been using it successfully.
https://deno.land/x/mongo/mod.ts