2 posts were split to a new topic: Docker: invalid reference format: repository name must be lowercase
Hey,
I decided to remove the docker, WSL and start from scratch - noticed that there was a new version of the storagenode image, so I was able and start my node, however, the output of the log was not particularly good:
2022-03-27T19:32:28.402Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "operator.email"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "contact.external-address"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "console.address"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "server.private-address"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "operator.wallet"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "storage.allocated-disk-space"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "server.address"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "storage.allocated-bandwidth"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file key {"Key": "operator.wallet-features"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file value for key {"Key": "log.caller"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file value for key {"Key": "log.development"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file value for key {"Key": "log.level"}
2022-03-27T19:32:28.402Z INFO Invalid configuration file value for key {"Key": "log.stack"}
2022-03-27T19:32:28.408Z INFO Running on version {"Service": "storagenode-updater", "Version": "v1.50.4"}
2022-03-27T19:32:28.409Z INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2022-03-27T19:32:28.428Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2022-03-27T19:32:28.435Z INFO Operator email {"Address": "MASKED"}
2022-03-27T19:32:28.435Z INFO Operator wallet {"Address": "MASKED"}
2022-03-27T19:32:29.065Z INFO Current binary version {"Service": "storagenode", "Version": "v1.50.4"}
2022-03-27T19:32:29.065Z INFO Version is up to date {"Service": "storagenode"}
2022-03-27T19:32:29.081Z INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.50.4"}
2022-03-27T19:32:29.081Z INFO Version is up to date {"Service": "storagenode-updater"}
2022-03-27 19:32:30,082 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-27 19:32:30,083 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-27 19:32:30,083 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-27T19:33:50.963Z INFO db database does not exist {"database": "reputation"}
2022-03-27T19:34:30.544Z INFO db database does not exist {"database": "notifications"}
2022-03-27T19:34:30.545Z INFO db database does not exist {"database": "heldamount"}
2022-03-27T19:34:30.545Z INFO db database does not exist {"database": "pricing"}
2022-03-27T19:34:30.545Z INFO db database does not exist {"database": "secret"}
2022-03-27T19:34:42.165Z INFO Telemetry enabled {"instance ID": "1mpseQ1dKctbLyQZxBz4KBjCHCVkQCPFx8wQKddneRp6oHa7Tz"}
2022-03-27T19:38:37.996Z INFO db.migration.23 Split into multiple sqlite databases
The new image autosets the allocated disk usage to 2TB, but in my case, I’m not able to allocate that much, so after the setup of the image I have edit the config.yaml file to 850GB as the space declared in my command.
I’m using Docker Desktop 4.6.1.
Not sure how to proceed based on the above.