ERR_CRYPTO_SCRYPT_NOT_SUPPORTED because nodejs was compiled without scrypt support

Open
#258 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
nodejs
Domain
devops

Research direction

Start by reproducing ERR_CRYPTO_SCRYPT_NOT_SUPPORTED in the relevant NodeJS container image and inspect how NodeJS is built in this repository. Done would require identifying a supported workaround for missing scrypt support or clarifying the image and build configuration that need to change.

Written by the indexing model from the issue text.

Description

How can one work around scrypt not being supported?

Dominant language
Shell
Stars
173
Forks
288
Avg merge
6d 1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sclorg/s2i-nodejs-container

All issues in sclorg/s2i-nodejs-container

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.