[image] Release v1.13.3 · storj/storj Changelog Storagenode [+ e63e596] storagenode/storagenodedb: allow existing dbs on setup [+ ec4c8dd] make: fix storagenode-updater binary target For Storage Nodes Bug Fix for installing a node with existing data We fixed t…

Files have been reuploaded. It seems that @littleskunk just accidentially picked the wrong release folder.

eleven more days before I get to see the improved dashboard :upside_down_face:has anyone been able to update docker nodes as of 10/4/20

how long ago mine didn’t 8 hours ago just waiting on watchtower for now

3 hours ago. The raspi is still not updated.

tho i’m sure it’s fine since v1.13.1 was held back and ended up being 1.13.3, but ill wait a couple of days to see if there is any crying… i’m sure it’s fine tho looking forward to the new features tho… so maybe take the plunge soon… :smiley:

My Docker Synology just updated but I had to recreate the container. It got deleted :frowning:

That sounds like a problem with watchtower on your end. Can you take a look at it’s logs?

wasn’t there something about watchtower needing to be updated when 1.13.1 was being rolled out or something like that…

I tried a manual update,docker pull storjlabs/storagenode:latest and this happened,latest: Pulling from storjlabs/storagenode Digest: sha256:ec3cea868ce23fb2e528d5232aa2ed535c10ab8bd6b67151f5033c6df9319d25 Status: Image is up to date for storjlabs/storagenode:latest docker.io/storjlabs/storageno…

watchtower may have already downloaded it but just not reinstalled the storagenode… you will need to run a docker rm storagenode and then your your run command else the new version will not be applied… because docker has an image or whatever its called loaded into the storagenode instance / conta…

Storj Community Forum (official)

Changelog v1.13.3

Product Discussions STORJLINGS

official-changelog

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled