Building Docker image is failing in Bitbucket CI/CD

[mhmh74072]

What happened?

• I can build a docker image locally, no issues.
• I can not build it properly in Bitbucket CI. The frontend building step is always failing.
• Frontend building step either times out OR
• It says the ./dist folder was created, but it is not showing up when using ls
• because ./dist folder is not available, the index.html can not be found on my AWS Fargate instance and the container fails
• If I create the image locally and push directly to AWS ECR, Fargate can run it without problems because the ./dist folder is available
• Also tried with Docker.multi, but no improvement. Stops at #50 673.3 ✓ 7547 modules transformed.

#6 102.1 created dist in 11s #6 102.7 #6 102.7 > [email protected] build:client-package #6 102.7 > cd packages/client && npm run build #6 102.7 #6 102.8 #6 102.8 > @librechat/[email protected] build #6 102.8 > npm run clean && rollup -c --bundleConfigAsCjs #6 102.8 #6 103.1 #6 103.1 > @librechat/[email protected] clean #6 103.1 > rimraf dist #6 103.1 #6 103.7 #6 103.7 src/index.ts → dist/index.js, dist/index.es.js... #6 131.9 created dist/index.js, dist/index.es.js in 28.1s #6 132.2 #6 132.2 > @librechat/[email protected] build #6 132.2 > cross-env NODE_ENV=production vite build && node ./scripts/post-build.cjs #6 132.2 #6 132.7 vite v6.3.4 building for production... #6 133.5 transforming... #6 133.7 Browserslist: browsers data (caniuse-lite) is 6 months old. Please run: #6 133.7 npx update-browserslist-db@latest #6 133.7 Why you should do it regularly: https://github.com/browserslist/update-db#readme #6 136.2 #6 136.2 warn - The class ease-[cubic-bezier(0.175,0.885,0.32,1.275)]is ambiguous and matches multiple utilities. #6 136.2 warn - If this is content and not a class, replace it withease-[cubic-bezier(0.175,0.885,0.32,1.275)]to silence this warning. #6 154.0 ../node_modules/react-virtualized/dist/es/WindowScroller/utils/onScroll.js (1:0): Module level directives cause errors when bundled, "no babel-plugin-flow-react-proptypes" in "../node_modules/react-virtualized/dist/es/WindowScroller/utils/onScroll.js" was ignored. #6 159.0 ../node_modules/vm-browserify/index.js (119:13): Use of eval in "../node_modules/vm-browserify/index.js" is strongly discouraged as it poses security risks and may cause issues with minification. #6 170.0 ✓ 7547 modules transformed. #6 395.0 npm error Lifecycle scriptbuildfailed with error: #6 395.0 npm error code 1 #6 395.0 npm error path /app/client #6 395.0 npm error workspace @librechat/[email protected] #6 395.0 npm error location /app/client #6 395.0 npm error command failed #6 395.0 npm error command sh -c cross-env NODE_ENV=production vite build && node ./scripts/post-build.cjs #6 395.2 npm warn config production Use--omit=devinstead. #6 405.5

Version Information

ghcr.io/danny-avila/librechat-dev-api latest 6c5edd195967 46 hours ago 2.21GB
ghcr.io/danny-avila/librechat-dev latest d7fc65a29a47 12 days ago 1.93GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite latest 42ef0aa9a8fa 3 weeks ago 2.02GB

Steps to Reproduce

1. Clone libre-chat repo
2. Push to repo
3. Build Docker image in Bitbucket pipeline

What browsers are you seeing the problem on?

No response

Relevant log output

>>Build command in use:
- docker build -t libre-chat-image .

>>bitbucket-pipelines file:
image: amazon/aws-cli:latest

definitions:
  services:
    docker:
      memory: 2048
  caches:
    docker-cliplugins: ~/.docker/cli-plugins

pipelines:
  default:
    - step:
        name: "Deploying to Dev"
        deployment: development
        image: amazon/aws-cli
        size: 8x
        oidc: true
        services:
          - docker
        script:
          - /bin/bash ci/create_deploy_docker_image.sh

>>Dockerfile:
# v0.8.0-rc1

# Base node image
FROM node:20-alpine AS node

# Install jemalloc
RUN apk add --no-cache jemalloc
RUN apk add --no-cache python3 py3-pip uv

# Set environment variable to use jemalloc
ENV LD_PRELOAD=/usr/lib/libjemalloc.so.2

# Add `uv` for extended MCP support
COPY --from=ghcr.io/astral-sh/uv:0.6.13 /uv /uvx /bin/
RUN uv --version

RUN mkdir -p /app && chown node:node /app
WORKDIR /app

USER node

COPY --chown=node:node . .

RUN \
    # Allow mounting of these files, which have no default
    touch .env ; \
    # Create directories for the volumes to inherit the correct permissions
    mkdir -p /app/client/public/images /app/api/logs ; \
    npm config set fetch-retry-maxtimeout 600000 ; \
    npm config set fetch-retries 5 ; \
    npm config set fetch-retry-mintimeout 15000 ; \
    npm install --no-audit; \
    # React client build
    NODE_OPTIONS="--max-old-space-size=2048" npm run frontend; \
    npm prune --production; \
    npm cache clean --force

RUN echo "--- ./client"
RUN ls ./client

RUN echo "--- ./dist"
RUN ls ./client/dist

RUN echo "--- ./app/client"
RUN ls ./app/client

RUN echo "--- ./dist"
RUN ls ./app/client/dist

RUN mkdir -p /app/client/public/images /app/api/logs

# Node API setup
EXPOSE 3080
ENV HOST=0.0.0.0
CMD ["npm", "run", "backend"]

# Optional: for client with nginx routing
# FROM nginx:stable-alpine AS nginx-client
# WORKDIR /usr/share/nginx/html
# COPY --from=node /app/client/dist /usr/share/nginx/html
# COPY client/nginx.conf /etc/nginx/conf.d/default.conf
# ENTRYPOINT ["nginx", "-g", "daemon off;"]

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Builds for Dockerfile and Dockerfile.multi are working as expected in Github CI/CD, I recommend using that even for a private fork.

https://github.com/danny-avila/LibreChat/actions/workflows/dev-images.yml

All repository files must be present in the build environment for it to work correctly. If the /dist folder and compiled assets are not present in the resulting image, it may be an issue with Bitbucket specifically.

[mhmh74072]

Thanks for the hint. I pushed the repo exactly as I cloned it, just with bitbucket-pipelines config and my Docker image creation script, but didn't change anything. Opened a ticket with Bitbucket now, otherwise I guess I'll keep pushing manually.