Container fails to build with Node 14 and bash script installation

Open
  • Is something wrong?
#15 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, dockerfile, node.js
Domain
build-system, devops

Research direction

Start with the repository's container build instructions and locate the Dockerfile that installs Node. Check whether the course projects support Node 18, update the installation approach or version as appropriate, then rebuild the container and verify the projects still work.

Written by the indexing model from the issue text.

Description

Describe the bug
The container doesn't build anymore because it tries to install Node 14 with a deprecated script. The bash scripts from NodeSource are deprecated. Also Node 14 is also deprecated, I guess that combination doesn't work anymore with the latest packages of Ubuntu 20.04.

To Reproduce
Steps to reproduce the behavior:
Try to re-build the container following the instructions from the repository.

Expected behavior
It builds :)

Desktop (please complete the following information):

  • OS: Windows 11 with Docker for Windows

Additional context
Replacing the installation of Node with new approach and using Node 18 seems to work.
No idea if the course projects would work with Node 18.

ENV NODE_MAJOR=18
RUN sudo apt-get update && \
  sudo apt-get install -y ca-certificates curl gnupg && \
  sudo mkdir -p /etc/apt/keyrings && \
  curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg && \
  echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list && \
  sudo apt-get update && \
  sudo apt-get install nodejs -y
Dominant language
Dockerfile
Stars
177
Forks
1.3k
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 freeCodeCamp/rdb-alpha

All issues in freeCodeCamp/rdb-alpha

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.