Multinode Dashboard Docker image

Node Operators getting started
, , ,
#1

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 :smiley:

Hope it helps anyone out there that make use of Docker-based environments.

7 Likes
#2

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
#3

Thank you for contribution!

1 Like
#4

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
#5

On qnap arm doesn’t work.
“The image don’t match……”

#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
#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
#8

Thanks everyone for your comments!

Awesome, just added to the README. Thanks!

I have just pushed the image for amd64, armv7 and armv8.
You can test it docker a 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.

3 Likes
#9

You can use the Multi stage build to avoid removing garbage.

1 Like