Quivr
-
|
Hi folks, i have been trying to run this on ubuntu server 24 proxmox CT with docker but i couldnt manage to get access even one time on the login page. It just wont load. While docker compose is going up im getting "web exited with code 0" tried to git pull, docker -build and everything i could find. plus docker compose logs web says "no such service: web" any workout idea? ~/quivr$ docker compose up |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
|
Hey, @wverdi! I'm here to help with any bugs or questions you have about the repository. Let's figure this out together! The To fix this, you can modify the services:
frontend:
image: quivr-frontend-prebuilt
pull_policy: never
build:
context: frontend
dockerfile: Dockerfile
args:
- NEXT_PUBLIC_ENV=local
- NEXT_PUBLIC_BACKEND_URL=${NEXT_PUBLIC_BACKEND_URL}
- NEXT_PUBLIC_SUPABASE_URL=${NEXT_PUBLIC_SUPABASE_URL}
- NEXT_PUBLIC_SUPABASE_ANON_KEY=${NEXT_PUBLIC_SUPABASE_ANON_KEY}
- NEXT_PUBLIC_CMS_URL=${NEXT_PUBLIC_CMS_URL}
- NEXT_PUBLIC_FRONTEND_URL=${NEXT_PUBLIC_FRONTEND_URL}
- NEXT_PUBLIC_AUTH_MODES=${NEXT_PUBLIC_AUTH_MODES}
container_name: web
depends_on:
- backend-core
restart: always
ports:
- 3000:3000
command: npm run dev # Add this line to start the Next.js serverMake sure that the |
Beta Was this translation helpful? Give feedback.
-
|
I've done this way on my docker-compose.yml services: backend-core: but ive got this error [+] Running 6/0 |
Beta Was this translation helpful? Give feedback.
-
|
The error you're encountering indicates that the To resolve this, you need to ensure that Node.js and FROM node:18.19.0-alpine AS base
# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat python3 make g++
RUN yarn global add node-gyp
WORKDIR /app
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN \
if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
elif [ -f package-lock.json ]; then npm ci; \
elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i --frozen-lockfile; \
else echo "Lockfile not found." && exit 1; \
fi
# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
ARG NEXT_PUBLIC_ENV
ARG NEXT_PUBLIC_BACKEND_URL
ARG NEXT_PUBLIC_SUPABASE_URL
ARG NEXT_PUBLIC_SUPABASE_ANON_KEY
ARG NEXT_PUBLIC_CMS_URL
ARG NEXT_PUBLIC_FRONTEND_URL
ARG NEXT_PUBLIC_AUTH_MODES # Make sure this is declared here if it influences the build
ENV NEXT_PUBLIC_ENV=$NEXT_PUBLIC_ENV
ENV NEXT_PUBLIC_BACKEND_URL=$NEXT_PUBLIC_BACKEND_URL
ENV NEXT_PUBLIC_SUPABASE_URL=$NEXT_PUBLIC_SUPABASE_URL
ENV NEXT_PUBLIC_SUPABASE_ANON_KEY=$NEXT_PUBLIC_SUPABASE_ANON_KEY
ENV NEXT_PUBLIC_CMS_URL=$NEXT_PUBLIC_CMS_URL
ENV NEXT_PUBLIC_FRONTEND_URL=$NEXT_PUBLIC_FRONTEND_URL
ENV NEXT_PUBLIC_AUTH_MODES=$NEXT_PUBLIC_AUTH_MODES
# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
# ENV NEXT_TELEMETRY_DISABLED 1
RUN yarn build
# If using npm comment out above and use below instead
# RUN npm run build
# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app
ENV NODE_ENV production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED 1
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
# Set the correct permission for prerender cache
RUN mkdir .next
RUN chown nextjs:nodejs .next
# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT 3000
# set hostname to localhost
ENV HOSTNAME "0.0.0.0"
ARG NEXT_PUBLIC_AUTH_MODES
ENV NEXT_PUBLIC_AUTH_MODES=$NEXT_PUBLIC_AUTH_MODES
# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
CMD ["node", "server.js"]Update your services:
frontend:
build:
context: frontend
dockerfile: Dockerfile
args:
- NEXT_PUBLIC_ENV=local
- NEXT_PUBLIC_BACKEND_URL=${NEXT_PUBLIC_BACKEND_URL}
- NEXT_PUBLIC_SUPABASE_URL=${NEXT_PUBLIC_SUPABASE_URL}
- NEXT_PUBLIC_SUPABASE_ANON_KEY=${NEXT_PUBLIC_SUPABASE_ANON_KEY}
- NEXT_PUBLIC_CMS_URL=${NEXT_PUBLIC_CMS_URL}
- NEXT_PUBLIC_FRONTEND_URL=${NEXT_PUBLIC_FRONTEND_URL}
- NEXT_PUBLIC_AUTH_MODES=${NEXT_PUBLIC_AUTH_MODES}
container_name: web
depends_on:
- backend-core
restart: always
ports:
- 3000:3000
command: npm run devThis should ensure that Node.js and |
Beta Was this translation helpful? Give feedback.
-
|
this is my docker-compose.yml updated my $path/frontend Dockerfile is this |
Beta Was this translation helpful? Give feedback.
-
|
It looks like your
Here's an updated version of your services:
frontend:
build:
context: frontend
dockerfile: Dockerfile
args:
- NEXT_PUBLIC_ENV=local
- NEXT_PUBLIC_BACKEND_URL=${NEXT_PUBLIC_BACKEND_URL}
- NEXT_PUBLIC_SUPABASE_URL=${NEXT_PUBLIC_SUPABASE_URL}
- NEXT_PUBLIC_SUPABASE_ANON_KEY=${NEXT_PUBLIC_SUPABASE_ANON_KEY}
- NEXT_PUBLIC_CMS_URL=${NEXT_PUBLIC_CMS_URL}
- NEXT_PUBLIC_FRONTEND_URL=${NEXT_PUBLIC_FRONTEND_URL}
- NEXT_PUBLIC_AUTH_MODES=${NEXT_PUBLIC_AUTH_MODES}
container_name: web
depends_on:
- backend-core
restart: always
ports:
- 3000:3000
command: ["node", "server.js"] # Ensure this matches the CMD in Dockerfile
backend-core:
image: stangirard/quivr-backend-prebuilt:latest
pull_policy: if_not_present
env_file:
- .env
build:
context: backend
dockerfile: Dockerfile
container_name: backend-core
extra_hosts:
- "host.docker.internal:host-gateway"
healthcheck:
test: [ "CMD", "curl", "http://localhost:5050/healthz" ]
command:
- "uvicorn"
- "quivr_api.main:app"Make sure to remove the Additionally, ensure that your This setup should ensure that the |
Beta Was this translation helpful? Give feedback.
-
|
ok, no errors now, but the login button in the login page doesnt work |
Beta Was this translation helpful? Give feedback.
-
|
To troubleshoot and fix the issue where the login button on the login page doesn't work, follow these steps:
Here is the relevant code snippet for reference: import { Page } from "@playwright/test";
export const login = async (page: Page): Promise<void> => {
const frontendUrl = process.env.NEXT_PUBLIC_E2E_URL;
const email = process.env.NEXT_PUBLIC_E2E_EMAIL;
const password = process.env.NEXT_PUBLIC_E2E_PASSWORD;
if (frontendUrl === undefined) {
throw new Error("NEXT_PUBLIC_E2E_URL is not defined");
}
if (email === undefined) {
throw new Error("NEXT_PUBLIC_E2E_EMAIL is not defined");
}
if (password === undefined) {
throw new Error("NEXT_PUBLIC_E2E_PASSWORD is not defined");
}
await page.goto(frontendUrl);
await page.getByTestId("login-button").first().click();
await page.getByPlaceholder("Email").fill(email);
await page.getByPlaceholder("Password").fill(password);
await page.getByTestId("submit-login").click();
await page.getByTestId("chat-page").isVisible();
};Additionally, based on the provided <div className="w-screen h-screen bg-ivory" data-testid="sign-in-card">
<main className="h-full flex flex-col items-center justify-center">
<section className="w-full md:w-1/2 lg:w-1/3 flex flex-col gap-2">
<Link href="/" className="flex justify-center">
<QuivrLogo size={80} color="black" />
</Link>
<p className="text-center text-4xl font-medium">
{t("talk_to", { ns: "login" })}{" "}
<span className="text-primary">Quivr</span>
</p>
<div className="mt-5 flex flex-col">
<FormProvider {...methods}>
<EmailLogin />
</FormProvider>
{googleSso && (password || magicLink) && (
<Divider text={t("or")} className="my-3 uppercase" />
)}
{googleSso && <GoogleLoginButton />}
</div>
<p className="text-[10px] text-center">
{t("restriction_message", { ns: "login" })}
</p>
</section>
</main>
</div>Ensure that the Finally, ensure your Docker setup is correct by verifying the FROM node:18.13.0-alpine
# Install Python and essential build tools
RUN apk add --update --no-cache python3 make g++ && ln -sf python3 /usr/bin/python
RUN python3 -m ensurepip
RUN pip3 install --no-cache --upgrade pip setuptools
# Create the directory on the node image
# where our Next.js app will live
RUN mkdir -p /app
# Set /app as the working directory
WORKDIR /app
# Copy package.json and yarn.lock
# to the /app working directory
COPY package*.json yarn.lock ./
# Install dependencies in /app
RUN yarn install --network-timeout 1000000
# Copy the rest of our Next.js folder into /app
COPY . .
# Ensure port 3000 is accessible to our system
EXPOSE 3000
# Run yarn dev, as we would via the command line
CMD ["yarn", "dev"]Make sure the Docker container is running and accessible on port 3000, as specified in the |
Beta Was this translation helpful? Give feedback.
-
|
This is my .env file |
Beta Was this translation helpful? Give feedback.
-
|
To resolve the issue where the login button on the login page doesn't work, follow these steps:
By following these steps, you should be able to identify and resolve the issue with the login button on the login page. |
Beta Was this translation helpful? Give feedback.
-
|
Worked like a charm, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Great to hear that it worked! If you have any more questions or need further assistance, feel free to ask. Happy coding! |
Beta Was this translation helpful? Give feedback.
To resolve the issue where the login button on the login page doesn't work, follow these steps:
Check Environment Variables:
Ensure that all necessary environment variables are correctly set in your
.envfile. Specifically, verify the following variables:NEXT_PUBLIC_BACKEND_URLNEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYNEXT_PUBLIC_AUTH_MODESYour
.envfile looks mostly correct, but ensure that the URLs and keys are accurate and accessible.Verify Network Requests:
Use the browser's developer tools to check for any network errors or failed requests when you click the login button. This can help identify if there are any issues with the API endpoints or CORS settings.
C…