Byrd
Byrd

Reputation: 907

How to bind to 0.0.0.0 instead of localhost for Docker purposes

I am currently trying to wrap the entire Node in a Docker container. However substrate when i run it runs on localhost. I cannot seem to find a way to bind it to 0.0.0.0 since Docker doesn't play too nice binding to localhost due to the nature of VMs being intermediary for a lot of environments.

Upvotes: 7

Views: 41327

Answers (3)

Eliott Teissonniere
Eliott Teissonniere

Reputation: 21

Use --ws-external / --rpc-external, you may also need to specify --rpc-cors all if you want to access it from the web

Upvotes: 2

Byrd
Byrd

Reputation: 907

Turns out substrate has two flags needed to bind to that interface. --ws-external and --rpc-external. Both of those will allow that.

Upvotes: 4

Artur Mruk
Artur Mruk

Reputation: 56

What do you mean by the entire node?

You should be able to bind it like this: --port 0.0.0.0:80:80 or use --network host (https://docs.docker.com/network/host/)

Upvotes: 4

Related Questions