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.
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.
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.
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.
I tried this docker image because the binary doesn’t allow me to add a node, the button doesn’t do anything. Either with this image. I tried with firefox and chrome and I can’t find what I’m missing.
Try to use a different browser - I checked and it works. Unless your node did not respond on requests though…
Try to open your external address with port in the browser.
For me it’s opened. However it’s possible that your router doesn’t have a hairpin NAT. In this case you need to use the local IP instead.