e486585853
We've had a lot of issues with alpine and currently there's a broken network issue on alpine for users running on RPI arm32 architechture which requires a workaround before docker is able to sync time between the host and the container: https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0\#time64_requirements. Since we're switching the base image of the storagenode to debian, it's best to switch the base image of all our docker images to debian as well for consistency; less drift across them and keeps the push target consistent. Change-Id: If3adf7a57dc59f19ef2221b892f340d919798fc5 |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| entrypoint | ||
| main_test.go | ||
| main.go | ||
| README.md | ||
Multinode Dashboard
Reference Articles
Generate identity files
In order to run this Docker image, you need to create an identity for the Multinode Dashboard. For this you need the binaries of the Identity Tool, which you can find in the latest version here:
https://github.com/storj/storj/releases/latest
In this example under Windows, we use the file identity_windows_amd64.zip, download it and unzip it.
Then we open a PowerShell window in the folder where the identity.exe was unzipped and run the following command:
./identity.exe create multinode --difficulty 10
If we run this command on Windows, the identity files will be created in the folder %appdata%\Storj\Identity\multinode.
Running the Multinode Dashboard in Docker
Then start the image like this, while replacing the directories marked by the < > with your parameters below:
docker run -d --restart unless-stopped \
--user $(id -u):$(id -g) \
-p 127.0.0.1:15002:15002/tcp \
--mount type=bind,source="<multinode-identity-dir>",destination=/app/identity \
--mount type=bind,source="<multinode-config-dir>",destination=/app/config \
--name multinode storjlabs/multinode:latest