[SOLVED] node 18 runtime error

[cobalt harbor]

I have appwrite running in WSL (win10).
After deploying a function, the build fails:

this error appears:
Docker Error: npm ERR! code EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/node-appwrite failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-04-13T23_42_01_039Z-debug-0.log

maybe a related issue:
https://github.com/appwrite/appwrite/issues/3812

[woeful scaffold]

Do you have your bridge network set to none?

[cobalt harbor]

No I don't

[woeful scaffold]

then maybe it's a unstable internet connection issue?

[cobalt harbor]

It is installed in a fresh WSL instance (ubuntu 20.04) and a new instance of appwrite

[cobalt harbor]

i made ping to google, <20ms

[woeful scaffold]

from where?

[cobalt harbor]

inside ubuntu (not inside the container)

[woeful scaffold]

you would need to test inside the runtime container. and nslookup registry.npmjs.org would be a better test

[cobalt harbor]

I will do it right now

[woeful scaffold]

here's a one-liner:

docker compose exec appwrite-executor docker run --rm openruntimes/node:v2-18.0 nslookup registry.npmjs.org

[cobalt harbor]

thank you

[cobalt harbor]

this is the result

I got the same result using portainer console

[woeful scaffold]

so that first one is the problem..im not sure why it can't resolve the domain name

[woeful scaffold]

what's the result of

docker compose exec appwrite-executor docker run --rm -it openruntimes/node:v2-18.0 sh

And then in the container:

cat /etc/resolve.conf

[cobalt harbor]

I will try to check what networks the container is connected

[woeful scaffold]

This might also be helpful to try:

docker compose exec appwrite-executor nslookup registry.npmjs.org

[cobalt harbor]

I did this: cat /etc/resolv.conf
result:

# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver 172.17.240.1

note the file name is resolv not resolve

[cobalt harbor]

Yeah nice idea, the result:

Server:         127.0.0.11
Address:        127.0.0.11:53

Non-authoritative answer:
Name:   registry.npmjs.org
Address: 104.16.16.35
Name:   registry.npmjs.org
Address: 104.16.24.35
...

[woeful scaffold]

Thats good it works in the executor...still bizarre it doesn't work in the runtime container...

[woeful scaffold]

Is there maybe an ip or subnet conflict with that ip address and another docker network or container?

[cobalt harbor]

I will check it on portainer

[cobalt harbor]

No there is no other network or ip

I've made a ping to the registry ip:
docker compose exec appwrite-executor docker run --rm openruntimes/node:v2-18.0 ping 104.16.16.35
it works

PING 104.16.16.35 (104.16.16.35): 56 data bytes
64 bytes from 104.16.16.35: seq=0 ttl=52 time=83.673 ms

but the name doesn't resolve D:

[woeful scaffold]

How did you set up/install Appwrite?

[cobalt harbor]

with the default docker compose yml, version 1.3.1
https://appwrite.io/install/compose

[woeful scaffold]

And what did you do with that?

And what about the .env file?

[cobalt harbor]

The .env file, the same as the official appwrite site.
https://appwrite.io/install/env

I change .env vars: secrets, runtimes (only node 18), db, etc

then I just do docker compose up -d

and successfully access to console and create databases and collections, also i run successfully with the cli

[woeful scaffold]

Sounds fine...

The only thing I can think of is a subnet/IP conflict. Otherwise, I'm not sure

[cobalt harbor]

Thank you so much for your time.
I will try to check the ips in windows and wsl

[woeful scaffold]

And docker subnets too

[cobalt harbor]

Ok

[cobalt harbor]

@woeful scaffold you are going to kill me 😅
I was reading this https://askubuntu.com/a/1419872 then i remember that i have a paid kaspersky in this laptop. I suspended it and it works.
I apologize, i have many laptops.

Now the build return:

added 10 packages, and audited 11 packages in 6s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities

[woeful scaffold]

Wow interesting...thanks for letting me know!

[cobalt harbor]

Thanks again

[SOLVED] node 18 runtime error

[cobalt harbor]

Hi Steven, I was digging inside the problem. I don't know how kaspersky was involved with wsl, but indeed there was a conflict with subnet ip.

docker0 ip-range si 172.17.0.0/16 and my wsl ip is 172.17.240.1 (the same that the runtime container is using for nameserver) that was the reason why "nslookup registry.npmjs.org". For docker 172.17.240.1 is a container.

I try to change wsl ip, but it seems easier to change docker0 ip-range. To change it I used daemon.json. For anyone who needs, here is a guide:
https://medium.com/codebrace/understanding-docker-networks-and-resolving-conflict-with-docker-subnet-ip-range-bfaad092a7ea

Thank you again, I hope this is useful for someone with the same problem.

[woeful scaffold]

This sort of makes sense...I'm still baffled at how Kaspersky fit in and why things worked after you turned it off 🧐

[cobalt harbor]

I think kaspersky block many things, i have node js in wsl and i was getting errors (that cannot connect to registry.npmjs.org when using npm install), other errors about self signed certs, etc etc.

[cobalt harbor]

Or kaspersky had nothing to do, and I made a mistake while trying to repair docker.

Other thing I noticed is that WSL has a dynamic IP, it changes after restart windows. But to avoid possible conflicts i will use daemon.json

[cobalt harbor]

The ip-range for WSL is 172.16.0.0/12 being the minimun 172.16.0.0 and the maximum 172.31.255.255
So the daemon.json ip-range should be 172.32.0.1/16 to avoid future conflicts