[Bug]: Container "0979d001b488" is unhealthy

No-Work-Team commented 9 months ago

What happened?

I am getting always the same error for both commands sudo docker-compose up --build and sudo docker-compose -f docker-compose.dev.yml up --build: Container "0979d001b488" is unhealthy (in my case 0979d001b488 = supabase/logflare:1.4.0 / supabase-analytics)

sudo docker logs 0979d001b488 <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution <<EOF: line 0: syntax error: EOF in backquote substitution

Does anybody know how to address/resolve this issue? Thanks in Advance.

Relevant log output

No response

Twitter / LinkedIn details

No response

dosubot[bot] commented 9 months ago

🤖

Hey there @No-Work-Team! I'm Dosu, a friendly bot here to lend a hand while we wait for a human maintainer. I can help you troubleshoot bugs, answer your questions, or guide you in becoming a contributor. It's like having a handy little helper in your pocket! So while we wait for a human, feel free to ask me anything. Now, let's see what we can do about your issue.

The error message you're seeing, "syntax error: EOF in backquote substitution", typically indicates a syntax error in your Dockerfile or docker-compose file. This could be due to a misplaced or missing backtick (`) or other syntax error.

Given the information you've provided, it's difficult to pinpoint the exact issue as the docker-compose file seems to be well-structured. However, the error might be coming from the Dockerfile which is not provided in the context.

Here are some general steps you can follow to debug this issue:

Check your Dockerfile and docker-compose file for any syntax errors. Make sure all backticks, quotes, and other special characters are correctly placed.
Ensure that all environment variables are correctly defined. If you're using backticks in an environment variable to execute a command, make sure the command is correct and can be successfully executed.
Try running the docker-compose commands with the --verbose flag to get more detailed output, which might help you identify the issue.
If you're still unable to resolve the issue, you might want to consider creating a minimal, reproducible example and asking for help on a Docker forum or Stack Overflow.

Without the Dockerfile and the exact line causing the error, it's hard to provide a more specific solution. If you could provide more details about your Dockerfile or the specific line causing the error, it would be easier to help you troubleshoot this issue.

For your reference, here is the Dockerfile used in the Quivr project:

FROM node:18.19.0-alpine AS base

FROM base AS deps
RUN apk add --no-cache libc6-compat python3 make g++
RUN yarn global add node-gyp
WORKDIR /app
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

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

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

RUN yarn build

FROM base AS runner
WORKDIR /app

ENV NODE_ENV production

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public
RUN mkdir .next
RUN chown nextjs:nodejs .next

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
ENV HOSTNAME "0.0.0.0"

CMD ["node", "server.js"]

This Dockerfile is used to create a Docker image for the Quivr project. It starts from a base image with Node.js installed, installs necessary dependencies, copies the application code into the image, builds the application, and finally sets up the production environment.

You can find the Dockerfile in the frontend directory of the Quivr repository.

I hope this helps! If you have any other questions or need further clarification, feel free to ask.

-Dosu

Sources

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

github-actions[bot] commented 6 months ago

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

QuivrHQ / quivr