Repository navigation
Closed
Description
There are two containers where the healthcheck fails in podman due to a syntax error, studio and pgmeta.
- pgmeta
Line 901 in 71c2abd
| Test: []string{"CMD", "node", `--eval='fetch("http://127.0.0.1:8080/health").then((r) => {if (r.status !== 200) throw new Error(r.status)})'`}, |
- studio
Line 947 in 71c2abd
| Test: []string{"CMD", "node", `--eval='fetch("http://127.0.0.1:3000/api/profile", (r) => {if (r.statusCode !== 200) throw new Error(r.statusCode)})'`}, |
When I change these two lines to a noop, the containers start successfully. For example:
- Test: []string{"CMD", "node", `--eval='fetch("http://127.0.0.1:8080/health").then((r) => {if (r.status !== 200) throw new Error(r.status)})'`},
+ Test: []string{"CMD", "node", `--version`},Log (it's not pretty):
Health:
FailingStreak: 2
Log:
- End: 2024-07-18T20:19:42.26441464+03:00
ExitCode: 1
Output: "[eval]:1\n'fetch(\"http://127.0.0.1:3000/api/profile\",\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nSyntaxError: Invalid or unexpected token\n at makeContextifyScript (node:internal/vm:185:14)\n at node:internal/process/execution:107:22\n at [eval]-wrapper:6:24\n at runScript (node:internal/process/execution:101:62)\n
alScript (node:internal/process/execution:133:3)\n at node:internal/main/eval_string:51:3\n\nNode.js v20.15.0"
Start: 2024-07-18T20:19:42.236295233+03:00
- End: 2024-07-18T20:19:52.356312244+03:00
ExitCode: 1
Output: "[eval]:1\n'fetch(\"http://127.0.0.1:3000/api/profile\",\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nSyntaxError: Invalid or unexpected token\n at makeContextifyScript (node:internal/vm:185:14)\n at node:internal/process/execution:107:22\n at [eval]-wrapper:6:24\n at runScript (node:internal/process/execution:101:62)\n
alScript (node:internal/process/execution:133:3)\n at node:internal/main/eval_string:51:3\n\nNode.js v20.15.0"
Start: 2024-07-18T20:19:52.328284657+03:00
Ref: #2359
Metadata
Metadata
Assignees
Labels
No labels
Activity
sweatybridge commentedon Jul 24, 2024
Could you report the podman version you are using? It seems fine on 5.0.2 based on the linked PR.
thenbe commentedon Jul 24, 2024
thenbe commentedon Jul 24, 2024
supabase-cli version: https://github.com/supabase/cli/tree/v1.187.3
Better error logs:
arvalaan commentedon Sep 3, 2024
Experiencing this as well on a fresh installation of everything.
Windows 11 (PowerShell)
Supabase CLI 1.191.3
Podman 5.2.2
Starting Supabase with --ignore-health-check allows for everything to work properly.
sweatybridge commentedon Sep 11, 2024
should be resolved by #2656 in
npx supabase@beta start