Docker image

Hi all,
I saw few posts here about Docker image, but I’ve never found one still maintained and used - even official documentation does not mention that there is one.
So I’ve made one, looks like it’s working (at least for me). For now it allows only to setup OWNER, but I’ll improve it in the future when it’ll be needed.
From other features it can be easily scaled using Docker features.

If you want to test it, feel free to pull from here
https://hub.docker.com/r/skenior/autonomi-node

Let me know if you have any issues or comments.
Thank you

10 Likes

Nice one @skenior
Check this out, just landed a couple of days ago :slight_smile:
its working well for me so far.

The docker image is working well, I still havent put UmbrelOS on anything yet.

2 Likes

Oh, that’s why I’ve missed it - thought it’s Docker image related to UmbrelOS, not to Autonomi itself. That one is robust, mine simply spins up safeup node, no GUI, just volumes for files and logs. Dead simple in comparison :slight_smile:

2 Likes

Nothing wrong with KISS :slight_smile:

Well, I’ll keep this image updated for now, maybe someone will need something simple. I’ll probably add few configuration features once I’ll have time for that, as this image is on alpine and only starts one node, it’s not resource intensive in any way (apart from how node itself needs resources). Maybe there will be some specific case when this is better

4 Likes

Disabled docker page for now, as I need to rework image for new settings

1 Like

Updated docker image with wallet address (instead of owner), but I have no idea if this will be good enough

2 Likes

Hey @skenior, thank you again for doing this!
Are you planning to update this to the new network iteration (happening today/tomorrow, apparently)?
I tested the image on Synology NAS and it seemed to work, although I’m not sure how to change port for single nodes, since I’m using the standard diskstation docker graphic interface, not composer.
Maybe @Eureka18 can chip in on that?

1 Like

@stout77 Docker image itself uses 42069 internally, and you can set up whatever port you’d like - you just need to redirect your port (let’s say 50000) to 42069 for image, everything else Docker will do automagically :slight_smile: Can’t say on if it’s possible on Synology, or how to set it up it there.
As for updating - of course, as soon as possible :slight_smile:

2 Likes

Great, thank you.
Just to clarify, for multiple containers, you would map, say
container 1, port 50000 to port 42069
container 2, port 50001 to same port 42069
And open ports 50000 and 50001 in the router to whatever is the IP of the docker host?

not big on docker cli myself. I can have a look though

1 Like

Exactly. 42069 is internal, and you can expose it with different value, like you said, port forward it from your router to the NAS and everything should work automagically :slight_smile:

2 Likes