Open JoshMcCullough opened 1 month ago
Can I ask where you pulled the images from?
I'm building the image myself using apps/meteor/.docker/Dockerfile
from this very repo, unaltered. The issue appears to be that some dep, which is being bumped
during yarn install
is requiring GLIBC 3+ whereas 2+ is what's available in the base image used to build the RC image.
docker buildx build -f apps/meteor/.docker/Dockerfile .
Kk. I'll try and get a comment on this.
asking internal eng team to check
We switched to the Alpine Dockerfile, which has GLIBC 3 and we are good for now. But we may "prefer" to move back to the non-Alpine image if/when this is resolved.
can i solve this issue?
is this still a problem?
This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed.
Description:
When pulling RC for the last 3 tagged releases (
6.10.6
,6.11.3
,6.12.1
) and then runningyarn --immutable
,yarn.lock
is being updated because multiple packages are newer in thepackage.json
files vs theyarn.lock
file.This leads to an install failure, because
yarn
can't install the wanted packages, since the lock file versions don't match those inpackage.json
.Furthermore, removing the
--immutable
flag will install the updated versions, which then break the Docker image due to an upgraded GLIBC requirementNote that
6.9.2
and6.9.7
also exhibit thepackage.json
/yarn.lock
inequality, but the resulting Docker images start correctly and do not have the GLIBC issue.Steps to reproduce:
yarn --immutable
-- build fails.yarn
-- build succeeds.Expected behavior:
The
yarn.lock
should never contain older versions than thepackage.json
files.Actual behavior:
The
yarn.lock
contains older versions than thepackage.json
files.Server Setup Information:
6.10.6
,6.11.3
,6.12.1
Client Setup Information