Inspecting Your Ratio1 Edge Node: Essential docker exec Commands
For Node Operators
Education
In the decentralized world of Ratio1, understanding and managing your Edge Node is crucial. Whether you're a developer, researcher, or enthusiast, having the right tools to inspect your node ensures optimal performance and integration within the Ratio1 network. This guide delves into the essential docker exec commands that provide insights into your node's status and performance.
Prerequisites
Before diving into the commands, ensure that you have a running Ratio1 Edge Node on your machine. There's no need for additional installations or configurations. The Edge Node operates within a Docker container, and all interactions can be performed using Docker commands. If you haven't set up your Edge Node yet, refer to our Getting Started Guide for detailed instructions.
Categorized Command Reference
Below is a comprehensive table detailing each available docker exec command for the Ratio1 Edge Node, including their descriptions and parameters:
Category | Command | Description | Parameter |
|---|---|---|---|
Information Retrieval | get_node_info | Retrieves the node's address, alias, Ethereum address, and version information. | None |
get_node_history | Provides performance metrics such as CPU load, memory usage, and GPU statistics. | None | |
get_startup_config | Displays the initial configuration parameters of the node. | None | |
get_config_app | Retrieves the current application configuration of the node. | None | |
get_allowed | Lists all addresses currently allowed to send tasks to the node. | None | |
get_e2_pem_file | Outputs the node's E2 PEM file content. | None | |
Configuration Management | add_allowed | Adds a specific address to the node's whitelist, allowing it to send computation tasks. | <address> (required), <alias> (optional) |
update_allowed_batch | Updates the whitelist with a batch of addresses. | <addresses> (required) | |
change_alias | Updates the node's alias (friendly name). Requires a container restart to take effect. | <new_alias> (required) | |
Reset and Maintenance | reset_address | Generates a new address for the node. | None |
reset_node_keys | Resets the node's cryptographic keys and generates a new address. Requires a container restart. | None | |
reset_supervisor | Resets the node's supervisor process. | None |
🛠️ Example Usage
Here are some practical examples of how to use these commands:
Retrieve Node Information:
You will get the following output:
Add an Allowed Address:
Change Node Alias:
And running get_node_info afterwards returns us the new name.
Petrica Butusina
May 20, 2025
