Followed by a screenshot of unhashed lines
You never said anything of the likes…
@Derkades pointed to your issue in the first response, which YOU then ignored. So it’s a little funny you tell me I’m ignoring you. People are trying to help but you keep denying that’s your issue. You also keep editing old posts which makes your updates really hard to follow.
Creating a new container does not create a new config as it’s stored outside the container.
Since you map the /app/config to your storage location, these two should literally be the same file. They can’t be different unless you’re looking at a different storage location than what your container is mapped to.
It looks like you’re using the wrong command for getting the dashboard. From the docs:
docker exec -it storagenode /app/dashboard.sh
If you’re using the storagenode binary directly like you are doing you will need to point it to the correct config location using
--config-dir. Have a look at the help too… but you really shouldn’t need that. Just follow the instructions in the documentation.
$ docker exec -it storagenode /app/storagenode --help
config Edit config files
dashboard Display a dashboard
diag Diagnostic Tool support
exit-satellite Initiate graceful exit
exit-status Display graceful exit status
help Help about any command
run Run the storagenode
setup Create config files
version output the version's build information, if any
--color use color in user interface
--config-dir string main directory for storagenode configuration (default "/root/.local/share/storj/storagenode")
--db.conn_max_lifetime duration Maximum Database Connection Lifetime, -1ns means the stdlib default (default -1ns)
--db.max_idle_conns int Maximum Amount of Idle Database connections, -1 means the stdlib default (default 20)
--db.max_open_conns int Maximum Amount of Open Database connections, -1 means the stdlib default (default 25)
--debug.addr string address to listen on for debug endpoints (default "127.0.0.1:0")
--debug.trace-out string If set, a path to write a process trace SVG to
--defaults string determines which set of configuration defaults to use. can either be 'dev' or 'release' (default "release")
-h, --help help for /app/storagenode
--identity-dir string main directory for storagenode identity credentials (default "/root/.local/share/storj/identity/storagenode")
--log.caller if true, log function filename and line number
--log.development if true, set logging to development mode
--log.encoding string configures log encoding. can either be 'console' or 'json' (default "console")
--log.level Level the minimum log level to log (default info)
--log.output string can be stdout, stderr, or a filename (default "stderr")
--log.stack if true, log stack traces
--metrics.addr string address to send telemetry to (default "collectora.storj.io:9000")
--metrics.app string application name for telemetry identification (default "storagenode")
--metrics.app-suffix string application suffix (default "-release")
--metrics.instance-prefix string instance id prefix
--metrics.interval duration how frequently to send up telemetry (default 1m0s)
--monkit.hw.oomlog string path to log for oom notices (default "/var/log/kern.log")
Use "/app/storagenode [command] --help" for more information about a command.
I’m really not a fan of how you’re treating people who are trying to help you. So I hope this posts helps you out, but I’m done after this.