dockerfile does not complete, saying "Docker Deployed"

[hubingkang]

To Reproduce

dockerfile does not complete, saying "Docker Deployed"

Current vs. Expected behavior

Complete all dockerfile steps

Provide environment information

FROM node:20-slim AS base
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN corepack enable
COPY . /app
WORKDIR /app

FROM base AS prod-deps
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --prod --frozen-lockfile

FROM base AS build
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile
RUN pnpm run build

FROM base
COPY --from=prod-deps /app/node_modules /app/node_modules
COPY --from=build /app/dist /app/dist
EXPOSE 8000
CMD [ "pnpm", "start" ]

Which area(s) are affected? (Select all that apply)

Docker

Additional context

Docker version 26.0.0, build 2ae903e

[Siumauricio]

The dockerfile looks good

1. does the application run once the build is finished?
2. Have you checked if that same image works for you locally first?

[hubingkang]

There is an error during docker deployment, but this log does not see the error message

[Siumauricio]

We use the native docker builder, so surely there is some error or suddenly we are not showing some important log that shows the error but for that I would need the following:

1. minimum repository with the minimum things to be able to test and reproduce the problem.

[thenglong]

@hubingkang Did you find a solution for this? I face the same issue at RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile

[Siumauricio]

@hubingkang Can you share the dockerfile and the project you are building?

[hubingkang]

@thenglong @Siumauricio I didn't use the dockerfile from pnpm

FROM node:20-slim AS base

RUN npm install -g pnpm

WORKDIR /app
COPY package.json pnpm-lock.yaml .npmrc ./
RUN pnpm install
COPY . .
RUN pnpm run build

Make sure you have the "package.json pnpm-lock.yaml.npmrc" files. If not, you'll get the same problem as above, but you won't see an error message.

[thenglong]

This is weird because I ran build dockerfile from pnpm instruction manually works but via Dokploy didn't. This is the line in Dockerfile that causes the problem in Dokploy

RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --prod --frozen-lockfile

[thenglong]

@hubingkang Shall we reopen this?

[hubingkang]

This is weird because I ran build dockerfile from pnpm instruction manually works but via Dokploy didn't. This is the line in Dockerfile that causes the problem in Dokploy

RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --prod --frozen-lockfile

Similarly, I successfully deployed it using docker directly on my computer

[Siumauricio]

It seems that the problem does not come from dokploy but from something external, checking very carefully in the logs locally it seems that it is something related to BuildKit that needs to be activated and comes from the dockerode library which we use to build the images when you use the Docker provider, according to investigating there seems to be an open issue about this,

apocas/dockerode#601
testcontainers/testcontainers-node#571

A solution will be to remove the --mount=type=cache

and use like this https://github.com/Dokploy/swarm-test/tree/dockerfile

FROM node:20-slim AS base
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN corepack enable
COPY . /app
WORKDIR /app

FROM base AS prod-deps
RUN pnpm install --prod --frozen-lockfile

FROM base AS build
RUN pnpm install --frozen-lockfile
RUN pnpm run build

FROM base
COPY --from=prod-deps /app/node_modules /app/node_modules
EXPOSE 3000
CMD [ "pnpm", "start" ]

[Siumauricio]

Since this is more of a dockerode issue, we can close it for now, when the issue is resolved we will update and the problem should go away, anyways there is a workaround for now