Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Dockerfile uses --openssl-legacy-provider flag for node #160

Closed
ChristophNiehoff opened this issue Nov 3, 2021 · 1 comment · Fixed by #167
Closed

Dockerfile uses --openssl-legacy-provider flag for node #160

ChristophNiehoff opened this issue Nov 3, 2021 · 1 comment · Fixed by #167

Comments

@ChristophNiehoff
Copy link
Collaborator

ChristophNiehoff commented Nov 3, 2021 •
edited
Loading

The dockerfiles recently got updated to node17.
This cut off support for old algorithms (see the release notes).
In our particular case, the problem is react-scripts that depends on an too-old version of webpack. See this discussion.

To make the app buildable with node17, the flag --openssl-legacy-provider was added to the client.dockerfile.

As soon as the new version of react-scripts is released, this flag should be removed again.
@ChristophNiehoff
Copy link
Collaborator Author

This also applies to the github action workflow.

@ChristophNiehoff ChristophNiehoff mentioned this issue Dec 13, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not use non-LTS nodejs runtime as docker base image dehydr8/elevation-of-privilege
1 participant
@ChristophNiehoff