2 years ago
Dockerfile:24
22 | # build phase 23 | COPY . /app/. 24 | >>> RUN --mount=type=cache,id=s/28f29262-5bea-4028-ab08-8b538bd0e9ee-next/cache,target=/app/.next/cache --mount=type=cache,id=s/28f29262-5bea-4028-ab08-8b538bd0e9ee-node_modules/cache,target=/app/node_modules/.cache npm run build 25 | 26 |
ERROR: failed to solve: process "/bin/bash -ol pipefail -c npm run build" did not complete successfully: exit code: 1
Error: Docker build failed
╔════════ Nixpacks v1.21.2 ═══════╗
║ setup │ nodejs_18, npm-9_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ build │ npm run build ║
║─────────────────────────────────║
║ start │ npm run start ║
╚═════════════════════════════════╝
ⓘ Deployment information is only viewable by project members and Railway employees.
2 Replies
2 years ago
Got my issue resolved
Here is how I resolve it:
Supabase client is not properly configured due to missing environment variables. Here are the steps to resolve this issue:
- Set up environment variables in Railway:
- Go to your Railway project dashboard.
- Click on the "Variables" tab.
- Add the following variables: NEXT_PUBLIC_SUPABASE_URL=your_supabase_project_url NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key Replace your_supabase_project_url and your_supabase_anon_key with the actual values from your Supabase project settings.
Status changed to Solved brody • almost 2 years ago