Hi all,
I have 1 node , that literally just wont update to 1.152.6 - all others have.
I run it via docker-run, and it fetches :latest - is there a way to force that to look at a new version? - I dont know the docker ‘versions’ as they are like hashes rather than numbers
current docker images are :
"latest"
"9109fd2-arm64v8"
"9109fd2-arm32v5"
"9109fd2-amd64"
"9109fd2"
"2159415-arm64v8"
"2159415-arm32v5"
"2159415-amd64"
"2159415"
"0c21bd6"
Thanks
Do nothing, leave the node alone. It will update when roll out reaches it. Container version is not related in any way with storagenode version.
Why do you want to force update in the first place?
1 Like
Stuck on the broken update of 1.152.5
Stop updater, download the node binary manually and replace the one in the container?
Alexey
April 25, 2026, 4:34am
5
You can stop and remove the container, remove the bin subfolder from the data location and run the container back.
Would you expect
docker system prune -f -a
To do this also ? Once stopped container , then to recreate it?
Alexey
April 25, 2026, 6:42am
7
No, just
docker stop -t 300 storagenode
docker rm storagenode
rm /mnt/storj/storagenode/storage/bin/*
docker run -d .... \
...
2 Likes