Can't get it to run via docker compose #19

c-wee · 2025-01-11T03:34:22Z

c-wee
Jan 11, 2025

Hi,
Tried to get it to run via docker compose but am failing to get it to run.
Go easy on me as I've a passing knowledge in self-hosting, but I get by by trial and error.

Changed the names of services db, app, cron to wapydb, wapyapp, wapycron respectively (along with updating the depends_on), though I suspect it's not the case.
As I have another service running on port 3000, I changed the port line to - '3210:3000'.

In .env, I added values to ID and SECRET keys to Github and Google, along with the RESEND API key. Left the rest alone.

Am I missing something?

Would rather run this via docker compose as it's easier in my set up. Have other services running smoothly with this method. Would really love to get this going as I'm a fan of shadn/ui components.

Thanks!

Edit: Update: Copied the whole repo into the docker compose directory but I just see a 404 page.

Looking at the logs for wapydev-app:

Dependencies are up to date...
Database schema is up to date, skipping migration...
Running in production mode...

> [email protected] build
> next build

   ▲ Next.js 15.1.2
   - Environments: .env

   Creating an optimized production build ...
(node:94) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:126) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 ✓ Compiled successfully
   Linting and checking validity of types ...
 ⨯ ESLint must be installed in order to run during builds: npm install --save-dev eslint
   Collecting page data ...
   Generating static pages (0/12) ...
   Generating static pages (3/12) 
   Generating static pages (6/12) 
   Generating static pages (9/12) 
 ✓ Generating static pages (12/12)
   Finalizing page optimization ...
   Collecting build traces ...

Route (app)                              Size     First Load JS
┌ ○ /_not-found                          986 B           107 kB
├ ƒ /app                                 12 kB          2.44 MB
├ ƒ /app/[slug]                          171 B          2.49 MB
├ ƒ /app/account                         8.3 kB          219 kB
├ ƒ /app/api/auth/[...nextauth]          143 B           106 kB
├ ƒ /app/api/cron                        143 B           106 kB
├ ƒ /app/api/mark-as-paid                143 B           106 kB
├ ƒ /app/contact                         5.89 kB         154 kB
├ ƒ /app/login                           6.23 kB         158 kB
├ ƒ /app/new                             171 B          2.49 MB
├ ƒ /app/privacy                         1.64 kB         114 kB
└ ƒ /app/reports                         4.27 kB        2.38 MB
+ First Load JS shared by all            106 kB
  ├ chunks/4bd1b696-23d7918caa53d4bd.js  53 kB
  ├ chunks/517-62ea556b5b071757.js       50.7 kB
  └ other shared chunks (total)          1.92 kB


○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand


> [email protected] start
> next start

   ▲ Next.js 15.1.2
   - Local:        http://localhost:3000
   - Network:      http://172.18.0.22:3000

 ✓ Starting...
 ✓ Ready in 635ms

tiagorvmartins · 2025-01-11T12:25:15Z

tiagorvmartins
Jan 11, 2025

Hey you can check this PR
Or directly clone:

git clone -b feature/production-docker-image https://github.com/tiagorvmartins/wapy.dev

Follow the new section on the README.md for production docker image and use the docker-compose.prod.yml

0 replies

meceware · 2025-01-11T15:29:50Z

meceware
Jan 11, 2025
Maintainer

It looks like the database connection is ready and everything should be working fine. What is your site URL? It might be related to that one.

0 replies

meceware · 2025-01-11T22:28:36Z

meceware
Jan 11, 2025
Maintainer

The main brach is updated to use docker images. I'm still testing but I hope you can help with it as well, to see if it solves your problem.

0 replies

c-wee · 2025-01-11T23:32:28Z

c-wee
Jan 11, 2025
Author

Thanks @tiagorvmartins and @meceware, I'm a ux/ui designer by day, so forgive me if I'm stuck at something trivial, or if some parts of my post makes no sense.

For a bit more context, my docker set up is running via Dockstarter through an override yaml file. Again, doing this because I'm not a dev. All the docker containers I've been running have been pre-compiled so it was easy for me to spin them up to get them running. That said, I'm not afraid of terminals/command lines.

With my set up, you're right in saying that the database is fine. In checking the db's docker logs, no errors appear. cron's logs however, shows a wget: bad address 'app:3000'.

Since my post, I've made port 3000 available for wapy.

I'll try starting everything from scratch with the latest release; will update after.

4 replies

tiagorvmartins Jan 12, 2025

@c-wee you mention this in your initial post:
"changed the names of services db, app, cron to wapydb, wapyapp, wapycron respectively"

if you notice this line there is app:3000, but you changed the name of the service correct? so you also need to update the app:3000 to <your_new_wapyapp_service_name>:3000 on that line.

Also I would suggest keeping the service name and container name equal, so there isn't confusions in case of doubt.
Let me know if you fix your problem, if not, post here the docker-compose, would be happy to help ;)

tiagorvmartins Jan 12, 2025

anyway if your issue is still 404 when opening the page, then something else is broken, if i am not mistaken is not related to the error your see on the cron service.

are you trying to reach the same machine ip on port exposed by the wapyapp service? or is it hosted somewhere else?

c-wee Jan 12, 2025
Author

changed the name of the service correct

@tiagorvmartins Thank you, that helped resolve the bad address error.

Started from scratch with the updated repo, and managed to be presented with the log in screen. I took your advice and had naming parity between containers and services. Only now, I am unable to sign in. I suspect there's a broken link to the database.

Here are logs:

From wapyapp:

Error: P1001: Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
Deploying database migrations...
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "$%7BPOSTGRES_DB%7D", schema "public" at "wapydb:5433"

Error: P1001: Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
Running server...
▲ Next.js 15.1.4

Local: http://localhost:3000

Network: http://0.0.0.0:3000

✓ Starting...
✓ Ready in 132ms
prisma:error
Invalid prisma.user.findUnique() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: PrismaClientInitializationError:
Invalid prisma.user.findUnique() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at Vn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7640)
at Vn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6663)
at Vn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6370)
at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9617)
at async r. [as getUserByEmail] (/app/.next/server/chunks/608.js:21:111718)
at async a_ (/app/.next/server/chunks/608.js:388:48586)
at async ax (/app/.next/server/chunks/608.js:388:49832)
at async aP (/app/.next/server/chunks/608.js:388:52383)
at async ak (/app/.next/server/chunks/608.js:388:56536)
at async aH (/app/.next/server/chunks/608.js:388:61835)
[auth][details]: {}
[auth][error] AdapterError: Read more at https://errors.authjs.dev#adaptererror
[auth][cause]: PrismaClientInitializationError:
Invalid prisma.user.findUnique() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at Vn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7640)
at Vn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6663)
at Vn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6370)
at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9617)
at async r. [as getUserByEmail] (/app/.next/server/chunks/608.js:21:111718)
at async a_ (/app/.next/server/chunks/608.js:388:48586)
at async ax (/app/.next/server/chunks/608.js:388:49832)
at async aP (/app/.next/server/chunks/608.js:388:52383)
at async ak (/app/.next/server/chunks/608.js:388:56536)
at async aH (/app/.next/server/chunks/608.js:388:61835)
[auth][details]: {}
⨯ h: Read more at https://errors.authjs.dev#adaptererror
at r. [as getUserByEmail] (.next/server/chunks/608.js:21:111747)
at async a_ (.next/server/chunks/608.js:388:48586)
at async ax (.next/server/chunks/608.js:388:49832)
at async aP (.next/server/chunks/608.js:388:52383)
at async ak (.next/server/chunks/608.js:388:56536)
at async aH (.next/server/chunks/608.js:388:61835)
at async p (.next/server/app/login/page.js:1:3362) {
type: 'AdapterError',
kind: 'error',
digest: '3986472767',
[cause]: [Object]
}
prisma:error
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
⨯ Error [PrismaClientInitializationError]:
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at async V (.next/server/app/api/cron/route.js:11:242) {
clientVersion: '6.2.1',
errorCode: undefined
}
⨯ Error [PrismaClientInitializationError]:
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at async V (.next/server/app/api/cron/route.js:11:242) {
clientVersion: '6.2.1',
errorCode: undefined
}
prisma:error
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
⨯ Error [PrismaClientInitializationError]:
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at async V (.next/server/app/api/cron/route.js:11:242) {
clientVersion: '6.2.1',
errorCode: undefined
}
⨯ Error [PrismaClientInitializationError]:
Invalid prisma.subscription.findMany() invocation:

Can't reach database server at wapydb:5433

Please make sure your database server is running at wapydb:5433.
at async V (.next/server/app/api/cron/route.js:11:242) {
clientVersion: '6.2.1',
errorCode: undefined
}

From wapydb

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/data -l logfile start
waiting for server to start....2025-01-12 01:03:43.498 UTC [49] LOG: starting PostgreSQL 17.2 (Debian 17.2-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-12 01:03:43.500 UTC [49] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-01-12 01:03:43.506 UTC [52] LOG: database system was shut down at 2025-01-12 01:03:43 UTC
2025-01-12 01:03:43.512 UTC [49] LOG: database system is ready to accept connections
done
server started
CREATE DATABASE

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2025-01-12 01:03:43.734 UTC [49] LOG: received fast shutdown request
waiting for server to shut down....2025-01-12 01:03:43.736 UTC [49] LOG: aborting any active transactions
2025-01-12 01:03:43.738 UTC [49] LOG: background worker "logical replication launcher" (PID 55) exited with exit code 1
2025-01-12 01:03:43.740 UTC [50] LOG: shutting down
2025-01-12 01:03:43.743 UTC [50] LOG: checkpoint starting: shutdown immediate
2025-01-12 01:03:43.786 UTC [50] LOG: checkpoint complete: wrote 921 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.022 s, sync=0.015 s, total=0.046 s; sync files=301, longest=0.002 s, average=0.001 s; distance=4238 kB, estimate=4238 kB; lsn=0/1908970, redo lsn=0/1908970
2025-01-12 01:03:43.792 UTC [49] LOG: database system is shut down
done
server stopped

PostgreSQL init process complete; ready for start up.

2025-01-12 01:03:43.863 UTC [1] LOG: starting PostgreSQL 17.2 (Debian 17.2-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-12 01:03:43.865 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-01-12 01:03:43.865 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-01-12 01:03:43.868 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-01-12 01:03:43.874 UTC [65] LOG: database system was shut down at 2025-01-12 01:03:43 UTC
2025-01-12 01:03:43.879 UTC [1] LOG: database system is ready to accept connections
2025-01-12 01:08:43.972 UTC [63] LOG: checkpoint starting: time
2025-01-12 01:08:48.435 UTC [63] LOG: checkpoint complete: wrote 47 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.428 s, sync=0.016 s, total=4.463 s; sync files=12, longest=0.013 s, average=0.002 s; distance=269 kB, estimate=269 kB; lsn=0/194C050, redo lsn=0/194BFE0

From wapycron

wget: server returned error: HTTP/1.1 500 Internal Server Error

And here's the docker compose extract:

container_name: wapydb
image: postgres:17.2
restart: unless-stopped
environment:
  - POSTGRES_USER=${POSTGRES_USER:-wapydev}
  - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
  - POSTGRES_DB=${POSTGRES_DB:-wapydev}
ports:
  - '5433:5432'
volumes:
  - ./wapydb:/var/lib/postgresql/data
wapyapp:
container_name: wapyapp
image: ghcr.io/meceware/wapy.dev:latest
restart: unless-stopped
env_file:
- .env
ports:
- '3000:3000'
depends_on:
- wapydb

wapycron:
container_name: wapycron
image: alpine:3.21
restart: unless-stopped
command: >
sh -c 'while true; do
/usr/bin/flock -n /tmp/wapy.lockfile wget -qO- wapyapp:3000/api/cron/;
sleep 60;
done'
depends_on:
- wapyapp

I changed the port of the db to 5433 as I have a paperless-ngx instance running (loads of troubleshooting with chatgpt here so it may in inaccurate). Let me know if I've been misguided.

Here's from .env

DATABASE_URL='postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@wapydb:5433/${POSTGRES_DB}?schema=public'

And here's the paperless-ngx extract in docker compose.

db:
image: docker.io/library/postgres:16
restart: unless-stopped
volumes:
- pgdata:/var/lib/postgresql/data
environment:
POSTGRES_DB: REDACTED
POSTGRES_USER: REDACTED
POSTGRES_PASSWORD: REDACTED

@meceware
Feedback: I'm of the opinion that the service names are unique. Then again, I'm not a dev so I don't know if my opinion here is valid. Initially ran into an issue here as I already had an existing service (db).

Additionally, I had to install npm, nvm (to update my nodejs) as I was unable to generate keys as my vm did not have/had an outdated npm/nvm/nodejs.

tiagorvmartins Jan 12, 2025

Change this:
DATABASE_URL='postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@wapydb:5433/${POSTGRES_DB}?schema=public'

To this:
DATABASE_URL='postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@db:5432/${POSTGRES_DB}?schema=public'

docker to docker talks through internal ports not the ones exposed, after swapping that should work I believe

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't get it to run via docker compose #19

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Can't get it to run via docker compose #19

c-wee Jan 11, 2025

Replies: 4 comments · 4 replies

tiagorvmartins Jan 11, 2025

meceware Jan 11, 2025 Maintainer

meceware Jan 11, 2025 Maintainer

c-wee Jan 11, 2025 Author

tiagorvmartins Jan 12, 2025

tiagorvmartins Jan 12, 2025

c-wee Jan 12, 2025 Author

tiagorvmartins Jan 12, 2025

c-wee
Jan 11, 2025

Replies: 4 comments 4 replies

tiagorvmartins
Jan 11, 2025

meceware
Jan 11, 2025
Maintainer

meceware
Jan 11, 2025
Maintainer

c-wee
Jan 11, 2025
Author

c-wee Jan 12, 2025
Author