Pull of latest image (for aarch64) failing

When I try to pull the latest beta I am seeing the following error:

storj@pine64 : ~ $ docker pull storjlabs/storagenode:beta
beta: Pulling from storjlabs/storagenode
no matching manifest for unknown in the manifest list entries

This is my OS/architecture information:

storj@pine64 : ~ $ docker info -f ‘{{.OSType}}/{{.Architecture}}’
linux/aarch64

Is there anyone monitoring this forum? My node has been offline now since yesterday because I followed the instructions on this page: https://documentation.storj.io/setup/software-updates that told me to stop then remove my storagenode container then simply pull the latest version down. I have not been able to pull this latest (beta) version down and posting to this forum has been no help at all. The help offered on the older now defunct group was much better.

Hi,
one day this happens to me with a rock64.

I was able to fix it doing:

1 enable

add --experimental to /lib/systemd/system/docker.service

ExecStart=/usr/bin/dockerd --experimental -H fd:// --containerd=/run/containerd/containerd.sock

2 reload

root@rock64:~# systemctl daemon-reload

3 restart

root@rock64:~# systemctl restart docker

4 check

root@rock64:~# docker version -f ‘{{.Server.Experimental}}’
true

5 pull

root@rock64:~# docker pull storjlabs/storagenode:beta --platform aarch64
beta: Pulling from storjlabs/storagenode
Digest: sha256:be11d66e0f1e3e9ac5932df75e8734b7cfcd0475cd5322e1a34f3be5765140f3
Status: Image is up to date for storjlabs/storagenode:beta
docker.io/storjlabs/storagenode:beta

6 check

root@rock64:~# docker image inspect 5f376c43c578 -f ‘{{.Architecture}}’
arm64

Regards

Thank you, thank you, thank you… this fixes the problem.

Now the web page should be updated to have this information :-).

My next question is whether this nearly 24hr outage will affect my Payout? Since as I mentioned it was cause by me following the instructions provided on the Storj webpage.

Try this tag: 1e8b9e7-v0.20.1-go1.12.9-aarch64 instead of beta

Thx @Alexey, however, the instructions from @edagner above already resolved my problem.

No, it’s affect only reputation for uptime. Your node would be selected rare until it recovered.