-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yarn.lock
is out of date, causing "CI" builds to fail.
#33367
Comments
Can I ask where you pulled the images from? |
I'm building the image myself using
|
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? |
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
The text was updated successfully, but these errors were encountered: