Install storagenode on QNAP 431XEU NAS

[and]

I also have a QNAP 431XEU for Storj, but I failed with the installation. So I wanted to share the drives from it with a PC running Node.

I downgraded the system to 4.5, installed Container Station, and the official Storj-Node. But I don’t know what to enter in the following places:

command

entrypoint

environment

network

device

shared folders

Can you recommend some instructions for those unfamiliar?

[Alexey]

I recommend to uninstall the app and use docker instead. The app is not maintained anymore and it’s a wrapper around docker anyway.

You may use this method:

Qnap Storagenode

To use Docker, in QNAP Container Station you can create an app, and then paste in the storage node docker compose config. This is how I run my node. I attached a screenshot here to show you what I mean: [image] You will need to ensure /share/Container/storj/storage and /share/Container/storj/identity go to the right place on the storage. If you SSH into the NAS it can be helpful to locate these paths. Alternatively you can follow the Docker steps here and do it all while in an SSH session.

The template of the docker-compose file, you need to replace all placeholders like <something> to the actual names and paths:

@mrkeyboardcommando

version: "3.3"
services:
  <containername>:
    image: storjlabs/storagenode:latest
    container_name: <containername>
    volumes:
      - type: bind
        source: <"/Path/to/identity/files">
        target: /app/identity
      - type: bind
        source: <"/Path/to/Data/storage/location">
        target: /app/config
    ports:
      - 28967:28967/tcp
      - 28967:28967/udp
      - 14002:14002
    restart: unless-stopped
    stop_grace_period: 300s
    environment:
      - WALLET=<WalletID>
      - EMAIL=<Emailaddress>
      - ADDRESS=<example.com:28967>
      - STORAGE=<1TB>
  watchtower:
    image: storjlabs/watchtower
    restart: always
    container_name: watchtower
    command: "<containername> watchtower --stop-timeout 300s --interval 21600"
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock

[and]

After many hours with chatgpt, I’ve written a script that doesn’t generate any errors. All files and folders are in the correct locations. Watchtower starts and works correctly, but Storj generates error 139 and constantly restarts.

version: “3.3”

services:
storj67:
image: storjlabs/storagenode:latest
container_name: storj67
volumes:

• type: bind
  source: /share/CACHEDEV5_DATA/Container/Identity/storagenode
  target: /app/identity
• type: bind
  source: /share/Public/storjdata
  target: /app/config
  ports:
• 28967:28967/tcp
• 28967:28967/udp
• 14002:14002
  restart: unless-stopped
  stop_grace_period: 300s
  environment:
• WALLET=0xCb96297D0B78f67889A3E6eA0A3B100ef2c527e2
• EMAIL=andpis@poczta.onet.pl
• ADDRESS=xxxxxxxxxxxx:28967
• STORAGE=8TB

watchtower:
image: storjlabs/watchtower
container_name: watchtower
restart: always
command: “storj67 watchtower --stop-timeout 300s --interval 21600”
volumes:

• /var/run/docker.sock:/var/run/docker.sock

i’m losing hope

[Roberto]

My docker run commands for multinodes on Synology NAS

These are all the useful parameters that one storagenode can use, and the modifications that I use for the second node. Fill free to use them or not, is up to you. I put them here fore easy reference. These work for Synology NAS and I run them in sudo su mode. There is also the --user $(id -u):$(id -g) parameter, but I started without it. It seems that dosen’t work on Synology NAS. OLD CONFIG: See UPDATED section for the recent version; also read the entire thread to get the picture. NODE 1…

[and]

for the next generations,

storj does not cooperate with procerors like annapurna

[arrogantrabbit]

@and

storj does not cooperate

with procerors like annapurna

Please elaborate. Amazon processors are arm64. They are fully supported by the go compiler.

What happens if you run it natively, forget docker nonsense.

Or are you talking about their older 32 bit processors? There have been issues in the past due to alignment. Maybe you are hitting something similar.

[Alexey]

What is says on

sudo uname -a

[batezippi]

Looks like its an old NAS with a 2016 CPU:

| CPU AnnapurnaLabs Alpine AL314 32-bit ARM® Cortex-A15 4-core 1.7GHz processor

CPU Architecture 32-bit ARM

[Alexey]

You may try to provide a platform as

services:
  storj67:
    container_name: storj67
    platform: linux/arm/v5
...

Do you have logs?

docker compose logs --tail 10 storj67

[and]

no logs, empty line
container doesn’t start

[Alexey]

Then it’s exactly this problem:

@arrogantrabbit

There have been issues in the past due to alignment. Maybe you are hitting something similar.

We use a newer Debian images, but they doesn’t support platforms with weird alignments.

Could you please try to run it directly without docker?
You need to setup a service if that’s allowed on Synology or run it as a start job maybe?
See

Run storagenode in Linux without Docker

Then you can try this one: There is also a method using Podman to generate an auto updating service: See also

[and]

Thanks for the help.
I wasted about 6 hours trying to get it working on QNAP and then gave up.
It took me 1 hour to get it working on Trunas.