[SOLVED] node 18 runtime error

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

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

I will check it on portainer

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

but the name doesn't resolve D:

How did you set up/install Appwrite?

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

And what did you do with that?

And what about the .env file?

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

Sounds fine...

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

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

And docker subnets too

Ok

@Steven 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:

Wow interesting...thanks for letting me know!

Thanks again

[SOLVED] node 18 runtime error

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.

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

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.

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

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

That sounds like a good plan 👍