Configurable or dynamic rpc_host
See original GitHub issueThere is currently an issue when running a chia node with the rpc server in a docker container. It is hard coded to listen on localhost.
This is based on one of the main ubuntu images and the /etc/hosts
it is like this:
localhost
is 127.0.0.1
which is the host machine and fails. I have given my container a hostname of chia
.
I think there are two potential ways to fix this;
- Work out the hostname/ip of the container instead of having a hardcoded
localhost
- Ability to configure
rpc_host
inconfig.yaml
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How to configure RPC to use certain ports and how to help ...
First, the RPC dynamic port range should be restricted to a smaller, more manageable port range that is easier to block by using...
Read more >Question: Using consul with dynamic ports #3436 - GitHub
I'm running three consul agent servers on mesos, the nodes get random hosts and ports accessible via environment variables HOST, PORT0, ...
Read more >Command-line options | Prysm
Below are all the available configuration parameters for the Prysm beacon node ... (default: 0) --rpc-host value Host on which the RPC server...
Read more >lnd.conf - Builder's Guide
The LND configuration file can be edited to customize your Lightning Network node. ... This is useful for users that only have a...
Read more >How to configure RPC dynamic port allocation to work with ...
Remote Procedure Call (RPC) dynamic port allocation is used by remote administration applications such as Dynamic Host Configuration ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
However your point is well taken and we’ll try to address it in this or the next release.
Closing as this has been fixed in the next release. Thanks guys.