maharifu
commented
2 weeks ago @taariq This link
lrwxrwxrwx 1 root root 30 Oct 11 13:49 /home/aaron/.config/paloma-lightnode/.paloma/config -> /root/lightnode/.paloma/configis wrong and should never be like that. We don't have it in the code to create the link like this, so I'm not sure how it happened. Can we ask the user to delete the file /home/aaron/.config/paloma-lightnode/.paloma/config and try again?
Also, regarding why are you guys forcing the usage of the root directory?, this is only used within docker. We do not use the root directory of the host system.
taariq
$ ./setup.sh automate v2: Pulling from palomachain/lightnode-client Digest: sha256:8fbf9d43a98880f4db1a50bf44a7fc1af88729b8eccb382d086bb04a454e4aba Status: Image is up to date for palomachain/lightnode-client:v2 docker.io/palomachain/lightnode-client:v2 Error: couldn't get client config: Config File "client" Not Found in "[/root/.paloma/config /root/lightnode/.paloma/config]" Usage: palomad config get [config] [key] [flags]
Flags: -h, --help help for get
Global Flags: --home string directory for config and data (default "/root/.paloma") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic|disabled or '*:,:') (default "info")
--log_no_color Disable colored logs
--trace print out full stack trace on errors
Error: couldn't get client config: Config File "client" Not Found in "[/root/.paloma/config /root/lightnode/.paloma/config]" Usage: palomad config set [config] [key] [value] [flags]
Flags: -h, --help help for set -s, --skip-validate skip configuration validation (allows to mutate unknown configurations) --stdout print the updated config to stdout -v, --verbose log changes to stderr
Global Flags: --home string directory for config and data (default "/root/.paloma") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic|disabled or '*:,:') (default "info")
--log_no_color Disable colored logs
--trace print out full stack trace on errors
Error: couldn't get client config: Config File "client" Not Found in "[/root/.paloma/config /root/lightnode/.paloma/config]" Usage: palomad config set [config] [key] [value] [flags]
Flags: -h, --help help for set -s, --skip-validate skip configuration validation (allows to mutate unknown configurations) --stdout print the updated config to stdout -v, --verbose log changes to stderr
Global Flags: --home string directory for config and data (default "/root/.paloma") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic|disabled or '*:,:') (default "info")
--log_no_color Disable colored logs
--trace print out full stack trace on errors
cat: /root/lightnode/.paloma/keys: No such file or directory Failed to unlock keys.
Aaron Caswell, [10/14/24 2:03 PM] why are you guys forcing the usage of the root directory?
Aaron Caswell, [10/14/24 2:03 PM] $ ls -la ~/.config/paloma-lightnode/.paloma/config lrwxrwxrwx 1 root root 30 Oct 11 13:49 /home/aaron/.config/paloma-lightnode/.paloma/config -> /root/lightnode/.paloma/config
Aaron Caswell, [10/14/24 2:03 PM] no one wants that bro