Docker Synology #63

xthephreakx · 2023-01-17T18:55:38Z

xthephreakx
Jan 17, 2023

this is no bug but a help request.

i ran the composer on my docker hosted on synology via portainer.
3 dockers are created succesfully and are up and running

but somehow i cant connect to the page am i missing something ? or do i need to do something after the dockers are created ?

javijuji · 2023-01-17T23:09:40Z

javijuji
Jan 17, 2023

Ran into the same issue. Seems like the app cant reach db at port 5432. Meanwhile db seems to be running correctly on port 5432 and listening to connections.

2023-01-17 23:07:05.801 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-01-17 23:07:05.801 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-01-17 23:07:05.851 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-01-17 23:07:05.927 UTC [25] LOG: database system was shut down at 2023-01-17 23:06:41 UTC
2023-01-17 23:07:05.954 UTC [1] LOG: database system is ready to accept connections

0 replies

oae · 2023-01-18T00:28:44Z

oae
Jan 18, 2023
Maintainer

I am also using docker on Synology. I believe the default network created by docker on Nas cannot resolve service names. Can you create a bridge network and use that?

0 replies

xthephreakx · 2023-01-18T16:25:58Z

xthephreakx
Jan 18, 2023
Author

Thnx for the tip I'll try that I'll keep you updated.

Update:

Added bridge network to 3 dockers. Rebooted docks and stil cannot connect.

Then removed the network created via kaizoku so that only bridge was available then Rebooted docks unfortunately same result.

0 replies

oae · 2023-01-18T17:31:42Z

oae
Jan 18, 2023
Maintainer

Can you try this guide?

https://drfrankenstein.co.uk/step-3-setting-up-a-docker-bridge-network/

0 replies

xthephreakx · 2023-01-18T18:46:37Z

xthephreakx
Jan 18, 2023
Author

created the bridge via the guide. still no joy.

didnt check the logfile of the dockers i'll supply them.

**kaizoku-db- **
PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-01-18 18:38:29.507 UTC [1] LOG: starting PostgreSQL 15.1 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit 2023-01-18 18:38:29.507 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-01-18 18:38:29.507 UTC [1] LOG: listening on IPv6 address "::", port 5432 2023-01-18 18:38:29.532 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-01-18 18:38:29.566 UTC [24] LOG: database system was shut down at 2023-01-18 18:38:01 UTC 2023-01-18 18:38:29.586 UTC [1] LOG: database system is ready to accept connections 2023-01-18 18:38:34.459 UTC [34] FATAL: role "kaizoku" does not exist 2023-01-18 18:38:39.533 UTC [41] FATAL: role "kaizoku" does not exist 2023-01-18 18:38:44.621 UTC [49] FATAL: role "kaizoku" does not exist 2023-01-18 18:38:49.698 UTC [56] FATAL: role "kaizoku" does not exist

kaizoku-redis-1
1:C 18 Jan 2023 18:38:30.143 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 18 Jan 2023 18:38:30.143 # Redis version=7.0.8, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 18 Jan 2023 18:38:30.143 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 1:M 18 Jan 2023 18:38:30.144 * monotonic clock: POSIX clock_gettime 1:M 18 Jan 2023 18:38:30.144 * Running mode=standalone, port=6379. 1:M 18 Jan 2023 18:38:30.145 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 1:M 18 Jan 2023 18:38:30.145 # Server initialized 1:M 18 Jan 2023 18:38:30.145 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1:M 18 Jan 2023 18:38:30.145 * Loading RDB produced by version 7.0.8 1:M 18 Jan 2023 18:38:30.145 * RDB age 28 seconds 1:M 18 Jan 2023 18:38:30.145 * RDB memory usage when created 0.82 Mb 1:M 18 Jan 2023 18:38:30.145 * Done loading RDB, keys loaded: 0, keys expired: 0. 1:M 18 Jan 2023 18:38:30.145 * DB loaded from disk: 0.000 seconds 1:M 18 Jan 2023 18:38:30.145 * Ready to accept connections

**kaizoku **
[19:45:33.083] ERROR (4285): Invalid prisma.manga.findMany()invocation: Can't reach database server atdb:5432Please make sure your database server is running atdb:5432. err: { "type": "PrismaClientInitializationError", "message": "\nInvalid prisma.manga.findMany()invocation:\n\n\nCan't reach database server atdb:5432\n\nPlease make sure your database server is running at db:5432.", "stack": Error: Invalid prisma.manga.findMany()` invocation:

      Can't reach database server at `db`:`5432`
      
      Please make sure your database server is running at `db`:`5432`.
          at RequestHandler.handleRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/index.js:34316:13)
          at RequestHandler.request (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/index.js:34293:12)
          at async PrismaClient._request (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/index.js:35273:16)
  "clientVersion": "4.6.1"
}

✓ set metadata.comic_info_xml to true
✓ set metadata.fetch_anilist to true
✓ set metadata.series_json to true
✓ set formats.use to cbz
✓ set downloader.download_cover to true
✓ set downloader.redownload_existing to true
✓ set downloader.chapter_name_template to [{padded-index}] {chapter}
✓ set downloader.create_manga_dir to true
✓ set downloader.create_volume_dir to false
✓ set downloader.stop_on_error to true
✓ set downloader.path to .`

0 replies

oae · 2023-01-18T18:48:39Z

oae
Jan 18, 2023
Maintainer

Can you share your exact docker-compose.yml file?

0 replies

xthephreakx · 2023-01-18T18:50:56Z

xthephreakx
Jan 18, 2023
Author

sure and thnx for the fast replies !

`version: '3'

volumes:
db:
redis:

services:
app:
container_name: kaizoku
image: ghcr.io/oae/kaizoku:latest
environment:
- DATABASE_URL=postgresql://kaizoku:kaizoku@db:5432/kaizoku
- KAIZOKU_PORT=3000
- REDIS_HOST=redis
- REDIS_PORT=6379
- UID=1038
- GID=65547
- TZ=Europe/Amsterdam
volumes:
- /volume1/docker/kaizoku/data:/data:rw
- /volume1/docker/kaizoku/config:/config:rw
- /volume1/docker/kaizoku/logs:/logs:rw
depends_on:
db:
condition: service_healthy
ports:
- '3000:3000'
redis:
image: redis:7-alpine
volumes:
- redis:/data
db:
image: postgres:alpine
restart: unless-stopped
healthcheck:
test: ['CMD-SHELL', 'pg_isready -U kaizoku']
interval: 5s
timeout: 5s
retries: 5
environment:
- POSTGRES_USER=kaizoku
- POSTGRES_DB=kaizoku
- POSTGRES_PASSWORD=kaizoku
volumes:
- db:/var/lib/postgresql/data
`

0 replies

xthephreakx · 2023-01-18T23:04:48Z

xthephreakx
Jan 18, 2023
Author

Oke another update I noticed in the composer that there are a DB and a REDIS volume declared so I made these folders and added the locations to the composer.

Only thing that gives errors now in the logs is kaizoku docker

_ Please make sure your database server is running at db:5432.
Can't reach database server at db:5432
[00:01:58.850] ERROR (5542):
err: {
"message": "\nInvalid prisma.manga.findMany() invocation:\n\n\nCan't reach database server at db:5432\n\nPlease make sure your database server is running at db:5432.",
"type": "PrismaClientInitializationError",
Error:
"stack":
"clientVersion": "4.6.1"
Invalid prisma.manga.findMany() invocation:
at RequestHandler.handleRequestError (/app/node_modules/.pnpm/@prisma [email protected][email protected]/node_modules/@prisma/client/runtime/index.js:34316:13)
at RequestHandler.request (/app/node_modules/.pnpm/@prisma [email protected][email protected]/node_modules/@prisma/client/runtime/index.js:34293:12)
at async PrismaClient._request (/app/node_modules/.pnpm/@prisma [email protected][email protected]/node_modules/@prisma/client/runtime/index.js:35273:16)

[00:02:34.588] ERROR (5881):
Please make sure your database server is running at db:5432.
Can't reach database server at db:5432
Invalid prisma.manga.findMany() invocation:
[00:02:46.191] ERROR (5994): _

0 replies

oae · 2023-01-20T16:40:10Z

oae
Jan 20, 2023
Maintainer

I tried it but I cannot reproduce this.

0 replies

xthephreakx · 2023-01-20T18:05:01Z

xthephreakx
Jan 20, 2023
Author

Damn that's unfortunate :(. Fixed another docker which couldn't communicate with my other container which was due to I had multiple gateways enabled on my nas. But it did t fix this issue I'll try it again from scratch after I brought the kids to bed.

0 replies

xthephreakx · 2023-01-20T22:57:06Z

xthephreakx
Jan 20, 2023
Author

Well I think fixing my gateway shizzle on the nas and redeploying the stack solved my problem :).

Thnx for the support. So I guess if anyone else has this issue on a synology nas they have to check if they have this setting set to enable cause that might brake some stuff....

0 replies

oae · 2023-01-20T23:02:18Z

oae
Jan 20, 2023
Maintainer

Nice.

2 replies

javijuji Jan 21, 2023

@xthephreakx
Still running into this issue and I did not have Enable Multiple Gateways enabled on my network settings. Could you share your working compose file?

xthephreakx Jan 21, 2023
Author

Sure thing.

It's posted above aswell.

version: '3'

volumes:
db:
redis:

services:
app:
container_name: kaizoku
image: ghcr.io/oae/kaizoku:latest
environment:
- DATABASE_URL=postgresql://kaizoku:kaizoku@db:5432/kaizoku
- KAIZOKU_PORT=3000
- REDIS_HOST=redis
- REDIS_PORT=6379
- UID=1038
- GID=65547
- TZ=Europe/Amsterdam
volumes:
- /volume1/docker/kaizoku/data:/data:rw
- /volume1/docker/kaizoku/config:/config:rw
- /volume1/docker/kaizoku/logs:/logs:rw
depends_on:
db:
condition: service_healthy
ports:
- 8316:3000
redis:
image: redis:7-alpine
volumes:
- /volume1/docker/kaizoku/redis:/data
db:
image: postgres:alpine
restart: unless-stopped
healthcheck:
test: ['CMD-SHELL', 'pg_isready -U kaizoku']
interval: 5s
timeout: 5s
retries: 5
environment:
- POSTGRES_USER=kaizoku
- POSTGRES_DB=kaizoku
- POSTGRES_PASSWORD=kaizoku
volumes:
- /volume1/docker/kaizoku/db:/var/lib/postgresql/data

javijuji · 2023-02-02T18:19:54Z

javijuji
Feb 2, 2023

@xthephreakx Did you run into any memory issues with this container on Synology? I've had things running smoothly for a few weeks now and Noticed my RAM usage increasing each day. As soon as the container is stopped/restarted it frees up about 6-7gb ram.

1 reply

xthephreakx Feb 2, 2023
Author

I did actually I've set a max of 4gb which helps

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker Synology #63

{{title}}

Replies: 13 comments 3 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Docker Synology #63

xthephreakx Jan 17, 2023

Replies: 13 comments · 3 replies

javijuji Jan 17, 2023

oae Jan 18, 2023 Maintainer

xthephreakx Jan 18, 2023 Author

oae Jan 18, 2023 Maintainer

xthephreakx Jan 18, 2023 Author

oae Jan 18, 2023 Maintainer

xthephreakx Jan 18, 2023 Author

xthephreakx Jan 18, 2023 Author

oae Jan 20, 2023 Maintainer

xthephreakx Jan 20, 2023 Author

xthephreakx Jan 20, 2023 Author

oae Jan 20, 2023 Maintainer

javijuji Jan 21, 2023

xthephreakx Jan 21, 2023 Author

javijuji Feb 2, 2023

xthephreakx Feb 2, 2023 Author

xthephreakx
Jan 17, 2023

Replies: 13 comments 3 replies

javijuji
Jan 17, 2023

oae
Jan 18, 2023
Maintainer

xthephreakx
Jan 18, 2023
Author

oae
Jan 18, 2023
Maintainer

xthephreakx
Jan 18, 2023
Author

oae
Jan 18, 2023
Maintainer

xthephreakx
Jan 18, 2023
Author

xthephreakx
Jan 18, 2023
Author

oae
Jan 20, 2023
Maintainer

xthephreakx
Jan 20, 2023
Author

xthephreakx
Jan 20, 2023
Author

oae
Jan 20, 2023
Maintainer

xthephreakx Jan 21, 2023
Author

javijuji
Feb 2, 2023

xthephreakx Feb 2, 2023
Author