Solved Docker restyaboard problem

Currently reading
Solved Docker restyaboard problem

Hey there

I tried to install restyaboard on my synology. But I keep having problems to get it running. I created the following docker-compose file:

YAML:
version: '2.2'

services:
  restyaboard_app:
    image: restyaplatform/restyaboard:v0.6.7
    networks:
      private: {}
    container_name: restyaboard_app
    environment:
      POSTGRES_DB: restyaboard
      POSTGRES_HOST: postgres
      POSTGRES_PASSWORD: admin
      POSTGRES_USER: admin
      TZ: 'Europe/Berlin'
      PUID: 1043
      PGID: 100
    volumes:
    - /volume1/docker/restya/app:/usr/share/nginx/html/media
    ports:
    - "6059:80"
    restart: unless-stopped

  restyaboard_db:
    image: postgres:12.2-alpine
    container_name: restyaboard_db
    networks:
      private:
    stop_grace_period: 1m30s
    environment:
      PGDATA: /var/lib/postgresql/data/pgdata
      POSTGRES_DB: restyaboard
      POSTGRES_HOST: postgres
      POSTGRES_PASSWORD: admin
      POSTGRES_USER: admin
    volumes:
    - /volume1/docker/restya/db/data:/var/lib/postgresql/data
    restart: unless-stopped
    
networks:
  private: {}

The restya container cant connect to the postgres container:
psql: could not translate host name "postgres" to address: No address associated with hostname

Maybe it is just a thing, but I do not get it right. Do you have a hint for me?

Kind regards!
 
In both containers?

Then he cannot connect:
Code:
psql: could not connect to server: Connection refused

Normally this setup worked with other containers.
 

Rusty

Moderator
NAS Support
6,095
1,785
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
In both containers?
Well Restya needs that variable for sure in order to connect to Postgres container. Personally I see no need to have those same variables in a postgres container as well. Apart from maybe

POSTGRES_USER
POSTGRES_PASSWORD
So imho HOST and PORT variables in Postgres container are not needed.
 
Ahhh I solved it. In the restya container settings. This was the false entry.
POSTGRES_HOST: postgres
It has to be the name of the db container name. Then the link will be created.
POSTGRES_HOST: restyaboard_db
 
Ok I'm shocked right now.
Why does this thing need so many anlytics and advertisement? Google, gstatic and doubleclick???

Does anybode know, how to disable it?
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Replies
3
Views
234
  • Question
If your NAS indeed is a DS416j, then I am afraid your memory is playing a trick on you. The cpu of the...
Replies
4
Views
814
  • Solved
That is interesting to know. Thank you! Probably nothing. And after some further consideration, I feel...
Replies
4
Views
317
  • Question
I haven't thought about it as a file system level cache. If it is, it would make sense that both benefit...
Replies
8
Views
302
I am struggling with that since I am only a copy & paste hacker. I have installed netdata on my Synology...
Replies
0
Views
154
OK, I have done those mappings (see screenshots). The status still shows the same error. File downloads...
Replies
3
Views
382
VPN, Tor, Tailscale, proxy, cell phone data... Not worth risking NAS and your network security IMO...
Replies
4
Views
311

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top