Hi SNOs,
I wanted to test the Multinode Dashboard Tech Preview, but I’m not a big fan of installing binaries (I know, it’s a Tech Preview).
So I have created an unofficial Docker image to run the Multinode Dashboard.
I have released the Dockerfile and additional scripts on this repository:
And I have pushed a built image on Docker Hub:https://hub.docker.com/r/odarriba/storj-multinode-dashboard
However, if you are familiar with Docker I would encourage you to build it by yourself using the GitHub repository. I’m a third party and you should not trust any third party by default
Hope it helps anyone out there that make use of Docker-based environments.
7 Likes
I’m not sure if this forum category is ok, or even if Storj is fine with this kind of unofficial packages.
If there is any problem or it is required to add any legal notice about Storj trademarks, just let me know!
1 Like
Alexey
September 10, 2021, 8:23am
#3
Thank you for contribution!
1 Like
This is awesome, thanks!
Btw, regarding the security considerations with the open port. You could change -p 15002:15002 to -p 127.0.0.1:15002:15002 in the docker command to still only have it open on local host, despite the 0.0.0.0 exposure inside the container.
2 Likes
Roberto
September 11, 2021, 9:07am
#5
On qnap arm doesn’t work.
SGC
September 11, 2021, 9:51am
#6
i would think the image needs to be built for a particular platform, even tho it’s sort of virtualized it’s a container, so it will utilize the baremetal installed OS as a foundation to overlay the top layer container stuff … or whatever one wants to call it.
pretty sure if you build the image from github as suggested, then it should work.
2 Likes
Roberto
September 11, 2021, 11:00am
#7
Yes, I figured it didn’t work, I reported my experience. Unfortunately, I don’t know enough about programming to do it myself
1 Like
Thanks everyone for your comments!
BrightSilence:
Btw, regarding the security considerations with the open port. You could change -p 15002:15002 to -p 127.0.0.1:15002:15002 in the docker command to still only have it open on local host, despite the 0.0.0.0 exposure inside the container.
Awesome, just added to the README. Thanks!
I have just pushed the image for amd64, armv7 and armv8.docker pull command first (or removing the image on your system before starting the container again).
I have no ARM device near me right now, if you can try it and post the result it would be awesome!
If there is someone interested in look how this cross build was archieved, it is using docker buildx and can be found on this commit
Also, I was previously leaving the zip files. Now they are removed and now the image is ~25 MiB in size.
4 Likes
Alexey
September 11, 2021, 5:24pm
#9
You can use the Multi stage build to avoid removing garbage.
1 Like
I made a PR for adding an official image here:
storj:main ← storj:sb/docker-multinode
opened 10:45PM - 20 Feb 22 UTC
Resolves https://github.com/storj/storj/issues/4547
We do not build an docker… image for the multinode dashboard,
which makes monitoring for docker-focused environments harder.
This adds the basic image and ties it into CI/CD.
Change-Id: I14c01a7f1f0019f6f5c1b8fd75dc424fc362b18d
## Code Review Checklist (to be filled out by reviewer)
- [ ] NEW: Are there any Satellite database migrations? Are they forwards _and_ backwards compatible?
- [ ] Does the PR describe what changes are being made?
- [ ] Does the PR describe why the changes are being made?
- [ ] Does the code follow [our style guide](https://github.com/storj/docs/blob/main/code/Style.md)?
- [ ] Does the code follow [our testing guide](https://github.com/storj/docs/blob/main/code/Testing.md)?
- [ ] Is the PR appropriately sized? (If it could be broken into smaller PRs it should be)
- [ ] Does the new code have enough tests? (*every* PR should have tests or justification otherwise. Bug-fix PRs especially)
- [ ] Does the new code have enough documentation that answers "how do I use it?" and "what does it do?"? (both source documentation and [higher level](https://github.com/storj/docs), diagrams?)
- [ ] Does any documentation need updating?
- [ ] Do the database access patterns make sense?
Based on the github issue made here:
opened 09:33PM - 18 Feb 22 UTC
Enhancement
Hello,
I would be happy if you could create a Docker image of the Multinode Das… hboard.
I know it is currently in tech preview and there are binaries. I would like to help and test it, but for me it would be more convenient to use Docker.
Thank you very much.
4 Likes
The image is live! You can follow the steps here:
# Multinode Dashboard
## Reference Articles
[Tech Preview Forum Post](https://forum.storj.io/t/tech-preview-multinode-dashboard-binaries/14572)
## Running in Docker
In order to run this docker image, you need to generate an identity like this:
```
identity create multinode --difficulty 10
```
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="<identity-dir>",destination=/app/identity \
show original
5 Likes
Works great, thanks for adding this! Makes it a lot easier to run this on Synology without getting in trouble with DSM updates.
1 Like
fr33tk
February 22, 2022, 12:43pm
#13
Have anyone experiencing issues “illegal base64 data at input byte 10” while adding storjnode to multinode, separate thread Nodes web api controller: illegal base64 data at input byte xx
