Unable to run stacker.news locally #917

SouthKoreaLN · 2024-03-02T14:23:12Z

SouthKoreaLN
Mar 2, 2024
Collaborator

Description
I wonder if the instructions here are still up to date. I don't seem to get the outcome that I would expect after running docker-compose up --build.

Steps to Reproduce
I followed the first two steps (installed docker-compose and cloned the project from github).

Expected behavior
I get these last 3 messages in my console logs. Attaching the full console logs here too.
log.txt

app exited with code 0
Gracefully stopping... (press Ctrl+C again to force)
dependency failed to start: container app exited (0)

I would expect the app not to exit so that I can access the site at localhost:3000.

Environment:
If you only experience the issue on certain devices or browsers, provide that info.

Device: Macbook Pro from 2019 (also tried on an older iMac, with same results).
Browser: Chrome

ekzyis · 2024-03-05T23:32:16Z

ekzyis
Mar 5, 2024

I wonder if the instructions here are still up to date. I don't seem to get the outcome that I would expect after running docker-compose up --build.

They should still work. I usually only run the database as a container and run the app and worker via npm run dev and npm run worker but I just tried out the docker setup with a fresh clone and it still works on my machine.

Looking at your logs, it seems like something is wrong with your database container:

db            | 2024-03-02 14:19:44.535 UTC [248] FATAL:  terminating connection due to administrator command

That's why the app container exits since it requires the db container to be up. I guess the same error shows up if you try to only get the database up with docker-compose up db? (--build only required for the app and worker)

0 replies

huumn · 2024-03-06T00:06:20Z

huumn
Mar 6, 2024
Maintainer

They should still work. I usually only run the database as a container and run the app and worker via npm run dev and npm run worker but I just tried out the docker setup with a fresh clone and it still works on my machine.

This is probably how we should setup our future dev env. Run app/worker locally and run all the other config-nightmare services in docker.

0 replies

SouthKoreaLN · 2024-03-06T00:23:24Z

SouthKoreaLN
Mar 6, 2024
Collaborator Author

Thanks for the answers.

docker-compose up db works, i.e. I am not getting the same error as when i include --build.

I'm trying the other approach. Currently managed to run the database as a container (docker-compose up db) and run the app (npm run dev ). Having some trouble with the worker though as it is telling me a specific table does not exist in my PostgreSQL database. I'll try to figure it out.

0 replies

SouthKoreaLN · 2024-03-06T00:32:24Z

SouthKoreaLN
Mar 6, 2024
Collaborator Author

Actually, while I was resolving the issues that i encountered when using the npm run worker approach, it now works when using the docker-compose up --build approach. I'm not sure what did the trick, I suspect it is because of the environment variable for OPENSEARCH, i.e. export OPENSEARCH_NODE which was export OPENSEARCH_URL on my system, but I can run SN locally at http://localhost:3000/. I do get another error at this point, but just thought of updating here before I waste more of your time.

EDIT: My hunch seems confirmed, I had to run export OPENSEARCH_URL=http://localhost:3000 before being able to run the container.

0 replies

huumn · 2024-03-06T00:33:44Z

huumn
Mar 6, 2024
Maintainer

Cool. I'm going be putting a lot of effort into making this as easy as I can soon. If you have any more feedback I'd appreciate it!

0 replies

SouthKoreaLN · 2024-03-06T00:38:30Z

SouthKoreaLN
Mar 6, 2024
Collaborator Author

Well, if you are ok with more feedback, the new error I get is this one:

Unhandled Runtime Error
TypeError: Failed to register a ServiceWorker for scope [('http://localhost:3000/')](http://localhost:3000/) with script [('http://localhost:3000/sw.js'):](http://localhost:3000/sw.js) ServiceWorker script evaluation failed

I checked that http://localhost:3000/sw.js is showing me something. I'll let you know if I solve it. This is all new to me, so I imagine I'll solve most by just digging a bit deeper.

EDIT: Seems like i need to locate the correct Locate the Correct Service Worker File.

0 replies

felipebueno · 2024-03-06T20:24:14Z

felipebueno
Mar 6, 2024
Collaborator

I tried mindlessly following the local development steps but it didn't work as well. It appears to be a different error so I'm not sure if I should open another issue.

I'll try to debug exactly where the error happens later but, for now, here's a (not that helpful) screenshot.

0 replies

felipebueno · 2024-03-06T20:33:33Z

felipebueno
Mar 6, 2024
Collaborator

One more screenshot. I think this one might be helpful:

Output for docker-compose up app

0 replies

felipebueno · 2024-03-07T12:09:55Z

felipebueno
Mar 7, 2024
Collaborator

Hey, @huumn, here's a more detailed output. Let me know if you need more details.

➜  stacker.news git:(master) sudo docker-compose up app
opensearch is up-to-date
db is up-to-date
Starting app ... done
Attaching to app
app             | npm verb cli /usr/local/bin/node /usr/local/bin/npm
app             | npm info using npm@9.6.7
app             | npm info using node@v18.17.0
app             | npm verb title npm install
app             | npm verb argv "install" "--loglevel" "verbose" "--legacy-peer-deps"
app             | npm verb logfile logs-max:10 dir:/root/.npm/_logs/2024-03-07T12_05_55_361Z-
app             | npm verb logfile /root/.npm/_logs/2024-03-07T12_05_55_361Z-debug-0.log
app             | npm verb reify failed optional dependency /app/node_modules/fsevents
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-win32-x64-msvc
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-win32-ia32-msvc
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-win32-arm64-msvc
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-linux-arm64-musl
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-linux-arm64-gnu
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-darwin-x64
app             | npm verb reify failed optional dependency /app/node_modules/@next/swc-darwin-arm64
app             | npm verb reify failed optional dependency /app/node_modules/@esbuild/darwin-arm64
app             | npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 608ms
app             | npm http fetch GET 200 https://registry.npmjs.org/request 9ms (cache hit)
app             | npm http fetch GET 200 https://registry.npmjs.org/nodemailer 11ms (cache hit)
app             | npm http fetch GET 200 https://registry.npmjs.org/tough-cookie 14ms (cache hit)
app             | npm http fetch GET 200 https://registry.npmjs.org/opentimestamps 3ms (cache hit)
app             | npm http fetch GET 200 https://registry.npmjs.org/request-promise 3ms (cache hit)
app             |
app             | up to date, audited 1599 packages in 2s
app             |
app             | 268 packages are looking for funding
app             |   run `npm fund` for details
app             |
app             | 5 moderate severity vulnerabilities
app             |
app             | To address issues that do not require attention, run:
app             |   npm audit fix
app             |
app             | To address all issues (including breaking changes), run:
app             |   npm audit fix --force
app             |
app             | Run `npm audit` for details.
app             | npm verb exit 0
app             | npm info ok
app             | node:internal/fs/utils:350
app             |     throw err;
app             |     ^
app             |
app             | Error: ENOENT: no such file or directory, open '/app/node_modules/.bin/prisma_schema_build_bg.wasm'
app             |     at Object.openSync (node:fs:603:3)
app             |     at Object.readFileSync (node:fs:471:35)
app             |     at ../../node_modules/.pnpm/@prisma+prisma-schema-wasm@5.4.1-2.ac9d7041ed77bcc8a8dbd2ab6616b39013829574/node_modules/@prisma/prisma-schema-wasm/src/prisma_schema_build.js (/app/node_modules/.bin/prisma:19032:31)
app             |     at __require (/app/node_modules/.bin/prisma:14:51)
app             |     at Object.<anonymous> (/app/node_modules/.bin/prisma:108112:42)
app             |     at Module._compile (node:internal/modules/cjs/loader:1256:14)
app             |     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
app             |     at Module.load (node:internal/modules/cjs/loader:1119:32)
app             |     at Module._load (node:internal/modules/cjs/loader:960:12)
app             |     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
app             |   errno: -2,
app             |   syscall: 'open',
app             |   code: 'ENOENT',
app             |   path: '/app/node_modules/.bin/prisma_schema_build_bg.wasm'
app             | }
app             |
app             | Node.js v18.17.0
app             |
app             | > stackernews@0.1.0 dev
app             | > NODE_OPTIONS='--trace-warnings' next dev
app             |
app             | node:internal/modules/cjs/loader:1080
app             |   throw err;
app             |   ^
app             |
app             | Error: Cannot find module '../server/require-hook'
app             | Require stack:
app             | - /app/node_modules/.bin/next
app             |     at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
app             |     at Module._load (node:internal/modules/cjs/loader:922:27)
app             |     at Module.require (node:internal/modules/cjs/loader:1143:19)
app             |     at require (node:internal/modules/cjs/helpers:110:18)
app             |     at Object.<anonymous> (/app/node_modules/.bin/next:6:1)
app             |     at Module._compile (node:internal/modules/cjs/loader:1256:14)
app             |     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
app             |     at Module.load (node:internal/modules/cjs/loader:1119:32)
app             |     at Module._load (node:internal/modules/cjs/loader:960:12)
app             |     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
app             |   code: 'MODULE_NOT_FOUND',
app             |   requireStack: [ '/app/node_modules/.bin/next' ]
app             | }
app             |
app             | Node.js v18.17.0
app exited with code 1

➜  stacker.news git:(master) sudo docker-compose up --build
[sudo] password for felipe:
Building db
[+] Building 1.1s (6/6) FINISHED                                                                                                                                                                      docker:default
 => [internal] load build definition from Dockerfile                                                                                                                                                            0.0s
 => => transferring dockerfile: 244B                                                                                                                                                                            0.0s
 => [internal] load metadata for docker.io/library/postgres:13.2                                                                                                                                                1.1s
 => [internal] load .dockerignore                                                                                                                                                                               0.0s
 => => transferring context: 2B                                                                                                                                                                                 0.0s
 => [1/2] FROM docker.io/library/postgres:13.2@sha256:0eee5caa50478ef50b89062903a5b901eb818dfd577d2be6800a4735af75e53f                                                                                          0.0s
 => CACHED [2/2] RUN apt-get update     && apt-get install --no-install-recommends -y postgresql-13-ip4r     && rm -rf /var/lib/apt/lists/*                                                                     0.0s
 => exporting to image                                                                                                                                                                                          0.0s
 => => exporting layers                                                                                                                                                                                         0.0s
 => => writing image sha256:34dc9ef518e85d4ec61094f28a36128c1bf741b1e8bf147023a4a5f3ff506647                                                                                                                    0.0s
 => => naming to docker.io/library/stackernews_db                                                                                                                                                               0.0s
Building app
[+] Building 2.3s (8/8) FINISHED                                                                                                                                                                      docker:default
 => [internal] load build definition from Dockerfile                                                                                                                                                            0.0s
 => => transferring dockerfile: 240B                                                                                                                                                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1                                                                                                                                                      1.1s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021                                                                                 0.0s
 => [internal] load metadata for docker.io/library/node:18.17.0-bullseye                                                                                                                                        1.0s
 => [internal] load .dockerignore                                                                                                                                                                               0.0s
 => => transferring context: 2B                                                                                                                                                                                 0.0s
 => [1/2] FROM docker.io/library/node:18.17.0-bullseye@sha256:7268327f2e3391b4c67337d55b2cd575f5e1ddc16ed2048a02e24ba4b1e03e8a                                                                                  0.0s
 => CACHED [2/2] WORKDIR /app                                                                                                                                                                                   0.0s
 => exporting to image                                                                                                                                                                                          0.0s
 => => exporting layers                                                                                                                                                                                         0.0s
 => => writing image sha256:56964c9514af2117104035660564e525dee9caee4359f2ca14ae78608170247c                                                                                                                    0.0s
 => => naming to docker.io/library/stackernews_app                                                                                                                                                              0.0s
Building worker
[+] Building 0.6s (8/8) FINISHED                                                                                                                                                                      docker:default
 => [internal] load build definition from Dockerfile                                                                                                                                                            0.0s
 => => transferring dockerfile: 146B                                                                                                                                                                            0.0s
 => resolve image config for docker.io/docker/dockerfile:1                                                                                                                                                      0.2s
 => CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021                                                                                 0.0s
 => [internal] load metadata for docker.io/library/node:18.17.0-bullseye                                                                                                                                        0.2s
 => [internal] load .dockerignore                                                                                                                                                                               0.0s
 => => transferring context: 2B                                                                                                                                                                                 0.0s
 => [1/2] FROM docker.io/library/node:18.17.0-bullseye@sha256:7268327f2e3391b4c67337d55b2cd575f5e1ddc16ed2048a02e24ba4b1e03e8a                                                                                  0.0s
 => CACHED [2/2] WORKDIR /app                                                                                                                                                                                   0.0s
 => exporting to image                                                                                                                                                                                          0.0s
 => => exporting layers                                                                                                                                                                                         0.0s
 => => writing image sha256:b8742e1c7e2f91cf0b67a756a6ad3bb62cce47d80d915b92fbeabfc6e9c645c6                                                                                                                    0.0s
 => => naming to docker.io/library/stackernews_worker                                                                                                                                                           0.0s
opensearch is up-to-date
db is up-to-date
Starting os-dashboard ... done
Starting app          ... done
Starting imgproxy     ... done

ERROR: for worker  Container "57cd6b377772" is unhealthy.
ERROR: Encountered errors while bringing up the project.

0 replies

huumn · 2024-03-07T21:22:46Z

huumn
Mar 7, 2024
Maintainer

If you want, checkout this branch: https://github.com/stackernews/stacker.news/tree/localdev

Then run ./sndev start

It has a number of refinements to the docker setup that should make it more reliable and deterministic (in addition to populating db/search with a seed).

0 replies

felipebueno · 2024-03-08T12:21:59Z

felipebueno
Mar 8, 2024
Collaborator

Cool, I'm trying it at this moment!

I'll tell how it went

Right away it's showing a couple db errors like this one:

...
db            | 2024-03-08 12:19:45.168 UTC [138] ERROR:  relation "users" does not exist at character 15
db            | 2024-03-08 12:19:45.168 UTC [138] STATEMENT:  SELECT 1 FROM users LIMIT 1
bitcoin       | 2024-03-08T12:19:45Z [http] Received a POST request for / from 172.18.0.5:41470
...

but I don't know if it's going to affect the final build

0 replies

felipebueno · 2024-03-08T12:28:05Z

felipebueno
Mar 8, 2024
Collaborator

I don't know if it's going to affect the final build

Hmm, it did!

Output for docker compose --env-file .env.sndev up db

0 replies

felipebueno · 2024-03-08T13:56:57Z

felipebueno
Mar 8, 2024
Collaborator

I'm trying to pinpoint where the problem happens but haven't found anything useful yet.

But this logical replication launcher error looks suspicious:

2024-03-08 13:47:39.024 UTC [1] LOG:  received fast shutdown request
2024-03-08 13:47:39.025 UTC [1] LOG:  aborting any active transactions
2024-03-08 13:47:39.026 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2024-03-08 13:47:39.027 UTC [27] LOG:  shutting down
2024-03-08 13:47:39.044 UTC [1] LOG:  database system is shut down

Full log:

➜  ~ docker logs 5b26b78096eb

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-03-08 12:18:34.640 UTC [1] LOG:  starting PostgreSQL 13.14 (Debian 13.14-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2024-03-08 12:18:34.641 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-03-08 12:18:34.641 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-03-08 12:18:34.643 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-08 12:18:34.648 UTC [26] LOG:  database system was shut down at 2024-03-08 12:18:22 UTC
2024-03-08 12:18:34.655 UTC [1] LOG:  database system is ready to accept connections
2024-03-08 12:18:44.680 UTC [47] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:18:44.680 UTC [47] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:18:54.767 UTC [62] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:18:54.767 UTC [62] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:04.841 UTC [77] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:04.841 UTC [77] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:14.921 UTC [92] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:14.921 UTC [92] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:25.002 UTC [107] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:25.002 UTC [107] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:35.085 UTC [123] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:35.085 UTC [123] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:45.168 UTC [138] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:45.168 UTC [138] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:19:55.287 UTC [153] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:19:55.287 UTC [153] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:05.360 UTC [169] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:05.360 UTC [169] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:15.488 UTC [184] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:15.488 UTC [184] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:25.618 UTC [199] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:25.618 UTC [199] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:35.737 UTC [215] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:35.737 UTC [215] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:45.860 UTC [230] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:45.860 UTC [230] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:20:55.973 UTC [245] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:20:55.973 UTC [245] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:06.075 UTC [261] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:06.075 UTC [261] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:16.185 UTC [276] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:16.185 UTC [276] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:26.311 UTC [291] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:26.311 UTC [291] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:36.429 UTC [307] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:36.429 UTC [307] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:46.546 UTC [322] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:46.546 UTC [322] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:21:56.654 UTC [337] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:21:56.654 UTC [337] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:06.777 UTC [353] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:06.777 UTC [353] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:16.905 UTC [368] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:16.905 UTC [368] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:27.026 UTC [383] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:27.026 UTC [383] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:37.159 UTC [399] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:37.159 UTC [399] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:47.273 UTC [414] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:47.273 UTC [414] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:22:57.385 UTC [429] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:22:57.385 UTC [429] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:07.497 UTC [445] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:07.497 UTC [445] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:17.599 UTC [460] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:17.599 UTC [460] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:27.702 UTC [475] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:27.702 UTC [475] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:37.817 UTC [491] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:37.817 UTC [491] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:47.930 UTC [506] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:47.930 UTC [506] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:23:58.034 UTC [521] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:23:58.034 UTC [521] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:08.137 UTC [537] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:08.137 UTC [537] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:18.262 UTC [552] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:18.262 UTC [552] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:28.393 UTC [567] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:28.393 UTC [567] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:38.514 UTC [583] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:38.514 UTC [583] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:48.636 UTC [598] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:48.636 UTC [598] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:24:58.757 UTC [613] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:24:58.757 UTC [613] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:08.870 UTC [629] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:08.870 UTC [629] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:18.998 UTC [644] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:18.998 UTC [644] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:29.105 UTC [659] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:29.105 UTC [659] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:39.228 UTC [675] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:39.228 UTC [675] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:49.352 UTC [690] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:49.352 UTC [690] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:25:59.470 UTC [705] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:25:59.470 UTC [705] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:26:09.594 UTC [721] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:26:09.594 UTC [721] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:26:19.721 UTC [736] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:26:19.721 UTC [736] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:26:29.839 UTC [751] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:26:29.839 UTC [751] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:26:39.947 UTC [767] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:26:39.947 UTC [767] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:26:50.035 UTC [782] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:26:50.035 UTC [782] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:27:00.158 UTC [797] ERROR:  relation "users" does not exist at character 15
2024-03-08 12:27:00.158 UTC [797] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 12:27:01.834 UTC [1] LOG:  received fast shutdown request
2024-03-08 12:27:01.835 UTC [1] LOG:  aborting any active transactions
2024-03-08 12:27:01.837 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2024-03-08 12:27:01.837 UTC [27] LOG:  shutting down
2024-03-08 12:27:01.851 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-03-08 13:46:52.962 UTC [1] LOG:  starting PostgreSQL 13.14 (Debian 13.14-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2024-03-08 13:46:52.962 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-03-08 13:46:52.962 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-03-08 13:46:52.965 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-08 13:46:52.969 UTC [26] LOG:  database system was shut down at 2024-03-08 12:27:01 UTC
2024-03-08 13:46:52.977 UTC [1] LOG:  database system is ready to accept connections
2024-03-08 13:47:02.998 UTC [47] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:47:02.998 UTC [47] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:47:13.087 UTC [62] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:47:13.087 UTC [62] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:47:23.170 UTC [78] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:47:23.170 UTC [78] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:47:33.230 UTC [93] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:47:33.230 UTC [93] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:47:39.024 UTC [1] LOG:  received fast shutdown request
2024-03-08 13:47:39.025 UTC [1] LOG:  aborting any active transactions
2024-03-08 13:47:39.026 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
2024-03-08 13:47:39.027 UTC [27] LOG:  shutting down
2024-03-08 13:47:39.044 UTC [1] LOG:  database system is shut down

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-03-08 13:48:25.460 UTC [1] LOG:  starting PostgreSQL 13.14 (Debian 13.14-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2024-03-08 13:48:25.469 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-03-08 13:48:25.469 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-03-08 13:48:25.475 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-08 13:48:25.480 UTC [26] LOG:  database system was shut down at 2024-03-08 13:47:39 UTC
2024-03-08 13:48:25.486 UTC [1] LOG:  database system is ready to accept connections
2024-03-08 13:48:35.490 UTC [47] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:48:35.490 UTC [47] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:48:45.612 UTC [62] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:48:45.612 UTC [62] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:48:55.713 UTC [78] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:48:55.713 UTC [78] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:05.824 UTC [93] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:05.824 UTC [93] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:15.909 UTC [108] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:15.909 UTC [108] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:25.991 UTC [124] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:25.991 UTC [124] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:36.100 UTC [139] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:36.100 UTC [139] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:46.214 UTC [154] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:46.214 UTC [154] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:49:56.335 UTC [170] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:49:56.335 UTC [170] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:06.454 UTC [185] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:06.454 UTC [185] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:16.557 UTC [200] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:16.557 UTC [200] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:26.641 UTC [216] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:26.641 UTC [216] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:36.730 UTC [231] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:36.730 UTC [231] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:46.856 UTC [246] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:46.856 UTC [246] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:50:56.968 UTC [262] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:50:56.968 UTC [262] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:07.089 UTC [277] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:07.089 UTC [277] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:17.175 UTC [292] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:17.175 UTC [292] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:27.291 UTC [308] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:27.291 UTC [308] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:37.394 UTC [323] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:37.394 UTC [323] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:47.518 UTC [338] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:47.518 UTC [338] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:51:57.635 UTC [354] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:51:57.635 UTC [354] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:52:07.761 UTC [369] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:52:07.761 UTC [369] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:52:17.877 UTC [384] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:52:17.877 UTC [384] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:52:27.996 UTC [400] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:52:27.996 UTC [400] STATEMENT:  SELECT 1 FROM users LIMIT 1
2024-03-08 13:52:38.104 UTC [415] ERROR:  relation "users" does not exist at character 15
2024-03-08 13:52:38.104 UTC [415] STATEMENT:  SELECT 1 FROM users LIMIT 1

0 replies

huumn · 2024-03-08T14:47:39Z

huumn
Mar 8, 2024
Maintainer

You probably need to delete all of your existing containers. The db container needs to be rebuilt so it imports the db seed.

0 replies

felipebueno · 2024-03-08T15:08:39Z

felipebueno
Mar 8, 2024
Collaborator

Oh, makes sense. I'll try!

Maybe adding a new command to sndev to reset the environment would help. Something like ./sndev reset or ./sndev clean or ./sndev bootstrap or something like that to delete all images and prune all containers related to Stacker News.

0 replies

felipebueno · 2024-03-11T17:39:58Z

felipebueno
Mar 11, 2024
Collaborator

Hmm, I tried it. It didn't work but now at least it thew a different error... Not sure yet if it's good or bad though 😅

Unfortunately I will not have time to help you debug it today but at least I can throw a couple screenshots here.

I also attached an asciinema recording with the output of sndev start. Maybe you could find something helpful by looking at it. You can unzip it and play it back with the asciinema play stacker_news.cast command.

stacker_news_recording.zip

0 replies

huumn · 2024-03-11T20:26:44Z

huumn
Mar 11, 2024
Maintainer

Can you share your browser versions when you get a chance?

0 replies

felipebueno · 2024-03-11T20:28:15Z

felipebueno
Mar 11, 2024
Collaborator

Can you share your browser versions when you get a chance?

0 replies

felipebueno · 2024-03-11T23:40:33Z

felipebueno
Mar 11, 2024
Collaborator

I'm trying to run the app part outside of docker to see if I can collect more details. To do that I removed && npm run dev from the Dockerfile, run sndev start, wait a few minutes and run npm run dev or npm run build from another terminal. I'm using using node 18.17, just like the docker image.

I'm still trying things out so, for now, I'm only attaching a few screenshots of the parts that might be useful for debugging here. Let me know if you see anything suspicious in the logs

0 replies

felipebueno · 2024-03-11T23:42:54Z

felipebueno
Mar 11, 2024
Collaborator

I think I'll try running it on a VM on QEMU or VirtualBox with a fresh install of Debian or Ubuntu or something.

@ekzyis @huumn which distro would you recommend for this purpose?

0 replies

ekzyis · 2024-03-12T06:05:46Z

ekzyis
Mar 12, 2024

I'm trying to run the app part outside of docker to see if I can collect more details. To do that I removed && npm run dev from the Dockerfile, run sndev start, wait a few minutes and run npm run dev or npm run build from another terminal. I'm using using node 18.17, just like the docker image.

I'm still trying things out so, for now, I'm only attaching a few screenshots of the parts that might be useful for debugging here. Let me know if you see anything suspicious in the logs

The following error means that the variables OPENSEARCH_USERNAME and OPENSEARCH_PASSWORD were not found in your environment:

ConfigurationError: Missing node(s) option

The error comes from here:

stacker.news/api/search/index.js

Lines 1 to 13 in 179a539

    
           import os from '@opensearch-project/opensearch' 
        
           const options = { 
        
             node: process.env.OPENSEARCH_URL, 
        
             auth: { 
        
               username: process.env.OPENSEARCH_USERNAME, 
        
               password: process.env.OPENSEARCH_PASSWORD 
        
             } 
        
           } 
        
           global.os = global.os || new os.Client(options) 
        
           export default global.os

which distro would you recommend for this purpose?

Mhh, I don't think we're doing anything special so I would say popular distros like Debian or Ubuntu sound like a good choice.

0 replies

felipebueno · 2024-03-12T11:43:49Z

felipebueno
Mar 12, 2024
Collaborator

Mhh, I don't think we're doing anything special so I would say popular distros like Debian or Ubuntu sound like a good choice.

Yeah, I tried on another machine with Lubuntu 22.04 and it gave me the same errors :/

Later today I'll try on another workstation with Debian 12. If it doesn't work, I'll try firing up a VM with a non-Debian based distro to see what happens... Maybe Fedora or Rocky Linux which are Red Hat based

0 replies

felipebueno · 2024-03-12T11:45:46Z

felipebueno
Mar 12, 2024
Collaborator

I also have a Mac Mini 2012 here somewhere. I think I'll try on it as well. Not today, maybe until the end of the week

0 replies

felipebueno · 2024-03-13T17:13:57Z

felipebueno
Mar 13, 2024
Collaborator

@huumn @ekzyis

I think there should be some documentation on how to run the app without using Docker. Better yet if it's not necessary to run all the parts, maybe just the app and the db.

Simple step-by-step instructions like "install node v18.x.x, PostgreSQL vX and etc"

I think it might make the dev environment easier to understand and get up and running, specially for devs without much experience that just want to make a quick small contribution

I'd like to help with that and I already started it by extracting the relevant parts from the docker-compose and Docker files. But I don't have much free time so it might take some time.

0 replies

felipebueno · 2024-03-16T01:28:58Z

felipebueno
Mar 16, 2024
Collaborator

@huumn @ekzyis

I'm trying with Docker again but now a new error has appeared. I still didn't have the time to try it on my mac mini

Something related with me not having valid credentials to download imgproxy from imgproxy.pro registry

I changed it from docker.imgproxy.pro/imgproxy:v3.23.0 to darthsim/imgproxy:v3.23.0 and (apparently) sndev start works again. By it works I mean it's doing stuff until the previous errors of this thread happens again.

0 replies

huumn · 2024-03-16T02:08:02Z

huumn
Mar 16, 2024
Maintainer

Oh weird. My understanding was that we could run imgproxy pro in dev without credentials. Hrm. Okay, I'll have to update that. Thanks!

0 replies

huumn · 2024-03-16T02:17:52Z

huumn
Mar 16, 2024
Maintainer

Okay, please pull and try again.

806f42e doesn't use imgproxy pro and sets the opensearch username and password now.

2 replies

felipebueno Mar 16, 2024
Collaborator

imgproxy working 👍

huumn Mar 16, 2024
Maintainer

what's failing

huumn · 2024-03-16T02:55:23Z

huumn
Mar 16, 2024
Maintainer

I believe I just fixed the service worker error in 56c2682

1 reply

felipebueno Mar 18, 2024
Collaborator

Yes, it's working!

It still throwing that CSP errors on Firefox but it's (apparently) working on Chrome. I'll play around with it later today

Thanks, @huumn

benalleng · 2024-03-25T13:50:07Z

benalleng
Mar 25, 2024
Collaborator

I seem to be getting lucky today and now I haven't gotten any failures to run on dev because of an unhealthy container since our conversation last night, but I'll keep an eye out and report back if I have any more issues.
I suspect that my computer being overloaded could have caused a timeout of sorts when trying to compile but we'll see

0 replies

securitybrahh · 2026-03-15T13:19:23Z

securitybrahh
Mar 15, 2026

on ./sndev start I am getting dependency failed to start: container app is unhealthy

upon running docker inspect --format='{{json .State.Health}}' app

I am seeing this error:

curl: (7) Failed to connect to localhost port 3000: Connection refused

I am running orbstack on mac m series

I edited the health command curl'ing google.com, though localhost:3000 doesn't have the site up

11 replies

huumn Mar 18, 2026
Maintainer

Looks like it got shutdown.

db | 2026-03-17T00:57:47.814669690Z 2026-03-17 00:57:47.814 UTC [1] LOG: received fast shutdown request

If you're dealing with claggy hardware, you may need to adjust the timeouts on many of the containers to give them enough time to pass healthchecks.

securitybrahh Mar 19, 2026

If you're dealing with claggy hardware, you may need to adjust the timeouts on many of the containers to give them enough time to pass healthchecks.

Oh not really, it shutdown because I stoped orbstack.

these are logs when its running - https://pastebin.com/N72VWTPJ

huumn Mar 19, 2026
Maintainer

I'm at a loss. Unless you've given incomplete app container logs, I'm not sure why the server isn't starting. It only depends on db which is coming up fine. This is what healthy app logs after yours end:

Datasource "db": PostgreSQL database "stackernews", schema "public" at "db:5432"

Already in sync, no schema change or pending migration was found.

)





> stackernews@0.1.0 dev
> NODE_OPTIONS='--trace-warnings --enable-source-maps' next dev

  ▲ Next.js 14.2.35
  - Local:        http://localhost:3000
  - Environments: .env.local, .env.development
  - Experiments (use with caution):
    · serverSourceMaps
    · scrollRestoration

 ✓ Starting...
   automatically enabled Fast Refresh for 1 custom loader
 ✓ Ready in 3.8s
 ✓ Compiled /middleware in 211ms (72 modules)
 ○ Compiling /~ ...
 ✓ Compiled /~ in 18.7s (4044 modules)

securitybrahh Mar 20, 2026

I created a feature, that was not loading I think, now when aI turn to master branch, it loads, but I think css is not loading for some reason

huumn Mar 20, 2026
Maintainer

If you are introducing changes that I don't have, that are breaking things in a way that you don't understand, I'm not sure how to help.

Uh oh!

Unable to run stacker.news locally #917

Uh oh!

Uh oh!

SouthKoreaLN Mar 2, 2024 Collaborator

Replies: 62 comments · 14 replies

Uh oh!

ekzyis Mar 5, 2024

Uh oh!

huumn Mar 6, 2024 Maintainer

Uh oh!

SouthKoreaLN Mar 6, 2024 Collaborator Author

Uh oh!

Uh oh!

SouthKoreaLN Mar 6, 2024 Collaborator Author

Uh oh!

huumn Mar 6, 2024 Maintainer

Uh oh!

Uh oh!

SouthKoreaLN Mar 6, 2024 Collaborator Author

Uh oh!

Uh oh!

felipebueno Mar 6, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 6, 2024 Collaborator

Uh oh!

felipebueno Mar 7, 2024 Collaborator

Uh oh!

huumn Mar 7, 2024 Maintainer

Uh oh!

Uh oh!

felipebueno Mar 8, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 8, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 8, 2024 Collaborator

Uh oh!

huumn Mar 8, 2024 Maintainer

Uh oh!

Uh oh!

felipebueno Mar 8, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 11, 2024 Collaborator

Uh oh!

huumn Mar 11, 2024 Maintainer

Uh oh!

felipebueno Mar 11, 2024 Collaborator

Uh oh!

felipebueno Mar 11, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 11, 2024 Collaborator

Uh oh!

ekzyis Mar 12, 2024

Uh oh!

felipebueno Mar 12, 2024 Collaborator

Uh oh!

Uh oh!

felipebueno Mar 12, 2024 Collaborator

Uh oh!

SouthKoreaLN
Mar 2, 2024
Collaborator

Replies: 62 comments 14 replies

ekzyis
Mar 5, 2024

huumn
Mar 6, 2024
Maintainer

SouthKoreaLN
Mar 6, 2024
Collaborator Author

SouthKoreaLN
Mar 6, 2024
Collaborator Author

huumn
Mar 6, 2024
Maintainer

SouthKoreaLN
Mar 6, 2024
Collaborator Author

felipebueno
Mar 6, 2024
Collaborator

felipebueno
Mar 6, 2024
Collaborator

felipebueno
Mar 7, 2024
Collaborator

huumn
Mar 7, 2024
Maintainer

felipebueno
Mar 8, 2024
Collaborator

felipebueno
Mar 8, 2024
Collaborator

felipebueno
Mar 8, 2024
Collaborator

huumn
Mar 8, 2024
Maintainer

felipebueno
Mar 8, 2024
Collaborator

felipebueno
Mar 11, 2024
Collaborator

huumn
Mar 11, 2024
Maintainer

felipebueno
Mar 11, 2024
Collaborator

felipebueno
Mar 11, 2024
Collaborator

felipebueno
Mar 11, 2024
Collaborator

ekzyis
Mar 12, 2024

felipebueno
Mar 12, 2024
Collaborator

felipebueno
Mar 12, 2024
Collaborator