ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE

[meme-lord]

Currently when you clone the repo and do docker compose up you will get this error

------
 > [front front-build 1/2] RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile:
1.765 ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-9.4.0.tgz
5.770 ! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing pnpm@9.4.0+sha512.f549b8a52c9d2b8536762f99c0722205efc5af913e77835dbccc3b0b0b2ca9e7dc8022b78062c17291c48e88749c70ce88eb5a74f1fa8c4bf5e18bb46c8bd83a.
5.770 ! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager
5.770
6.207  ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE  Cannot perform a frozen installation because the version of the lockfile is incompatible with this version of pnpm
6.207
6.207 Try either:
6.207 1. Aligning the version of pnpm that generated the lockfile with the version that installs from it, or
6.207 2. Migrating the lockfile so that it is compatible with the newer version of pnpm, or
6.207 3. Using "pnpm install --no-frozen-lockfile".
6.207 Note that in CI environments, this setting is enabled by default.
------
failed to solve: process "/bin/sh -c pnpm install --frozen-lockfile" did not complete successfully: exit code: 1

I did a quick patch by removing --frozen-lockfile from the command in server/docker/front/Dockerfile but updating the pnpm-lock.yaml is probably the correct thing to do, I just don't know how to do it.

[dumprop]

I think it would be better to just downgrade the pnpm version because updating the pnpm-lock.yaml may introduce some regressions

[AndersFelde]

Adding this to the front-base docker image build worked for me

RUN corepack use pnpm@8.x

[Waariss]

Thanks @AndersFelde you save my life