Docker compose based node not starting

It already checked, working fine :slight_smile:

You should either forward the 28967 or change the external port in the address

1 Like

yeah… i think i saw it at the same moment :
Storage Node Dashboard ( Node Version: v1.6.4 )

======================

ID           13KK1Q2P2pz1oMTEQ5nzAfRWqJFTvaPUe9sfzmorhEPecfbwc7
Last Contact OFFLINE
Uptime       40m12s

                   Available     Used     Egress     Ingress
     Bandwidth           N/A      0 B        0 B         0 B (since Jul 1)
          Disk        3.3 TB      0 B
Internal 127.0.0.1:7778
External datacenter.orionbrigade.ovh:28967

can you post boath nodes config? does they on same pc?

External datacenter.orionbrigade.ovh:28967 should be
External datacenter.orionbrigade.ovh:28968

they do not live on the same host no.

The old one is a Rock64
This one is x86-64 based

This node is the only one using docker-compose in combination with Storjnode

if folow this picture in pfsence https://docs.netgate.com/pfsense/en/latest/book/nat/ordering-of-nat-and-firewall-processing.html
you shold open boath ports on firewall

28967 is forwarded to 10.88.10.5:28967
28968 if NAT redirect to 10.88.10.1:28967

But we have liftoff:

Please, change the ADDRESS in your yaml then and restart the service

docker-compose restart -t 300 storagenode-Node1

Perhaps it’s worth to add stop_grace_period: 300s to your docker-compose.yaml

For the ones looking for a docker-compose.yml file:

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 
      - 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

Thanks guys!
Sometimes you just need a nudge in the right direction!

4 Likes

thanks, i added it in the above version… is this right?

Yes, looks good.
Is it online?

It seems to be online.

Thanks!

1 Like

I saw this thread being mentioned somewhere… but the docker-compose.yml is outdated.

I’ll update it right now!

I cannot seem to edit the old config… or delete it.
@moderator : please hide/delete previous source yaml

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: unless-stopped
    container_name: watchtower
    command: "<containername> watchtower --stop-timeout 300s --interval 21600"
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock
1 Like

Thank you for update! I changed the first post to a wiki, so now you should be able to edit it.

The first yaml is now also updated. and there is a solution pinned.

If anyone needs help setting up his/her Docker container via docker-compose, just write me a message.
I am not around any day, but when i see the message, i’ll reply!

1 Like

Is it possible to put multiple Dockers into one Docker-Compose?

Like a STORJ-Docker and a STORJ-Exporter-Docker? Can you tell about the auto/restart of the compose? When is the file beeing read and executed?

Yes, you can do it. Each container can have an own policy regarding restarts.
So if you specify, that it should be restarted, it will be restarted.

Yes, I do just that in my deployment.

1 Like