-
Notifications
You must be signed in to change notification settings - Fork 2k
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
node:18 (bookworm) lacks libcrypto.so.1.1 present in previous releases such as 18-bullseye #1916
Comments
See if this helps |
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-whats-new.en.html#newdistro |
Worked for me too with 18-bullseye. For anyone new to CircleCi like me, here's my entire config.yml # fonud here https://pnpm.io/continuous-integration
version: 2.1
jobs:
build: # this can be any name you choose
docker:
- image: node:18-bullseye #raw 18 fails: https://github.com/nodejs/docker-node/issues/1916
resource_class: large
parallelism: 10
steps:
- checkout
- restore_cache:
name: Restore pnpm Package Cache
keys:
- pnpm-packages-{{ checksum "pnpm-lock.yaml" }}
- run:
name: Install pnpm package manager
command: |
corepack enable
corepack prepare pnpm@latest-8 --activate
- run:
name: Install Dependencies
command: |
pnpm install
- save_cache:
name: Save pnpm Package Cache
key: pnpm-packages-{{ checksum "pnpm-lock.yaml" }}
paths:
- node_modules
- run:
name: Test with jest
command: |
node --experimental-vm-modules node_modules/jest/bin/jest.js |
Having this issue with node:20, trying to use a different image. UPDATE: running node:20-buster - from docker hub solves the issue. |
I just tried with Bullseye 22 (the latest version) and it works. This also solves the problem with Node 20 and the slow tests. |
libcrypto was not explicitly installed from any of the images on which Node images are built. It likely was included in bullseye as a transitive dependency of one of the buildpack-deps package installed and that package doesn't rely on libcrypto anymore in bookworm and more recent versions. If you explicitly depend on that library, I would strongly recommend adding it to your Dockerfile. |
Environment
Expected Behavior
libcrypto.so.1.1 is findable on the system with node:18-bullseye
Current Behavior
libcrypto.so.1.1 is not present
Possible Solution
This started happening after the recent update to bookworm and installing node:18-bullseye works as expected
Steps to Reproduce
Additional Information
This breaks any CI that uses node:18 and https://github.com/nodkz/mongodb-memory-server as the mongodb binary requires libcrypto.so.1.1
The text was updated successfully, but these errors were encountered: