LTS Node 18.18.1 is not supported (missing image in docker hub)

[mlandisbqs]

Environment

• Platform: any
• Docker Version: any
• Node.js Version: 18.18.1
• Image Tag: node:18.18.1-alpine

Expected Behavior

Our CI Pipeline validates that our software runs on LTS. When LTS changes we upgrade our packages. Part of the team's build process relies on the docker images for node being available for LTS with an assumption that LTS would be supported and promptly available in docker hub. We've never had an issue before but the build is breaking because this version has not been published.

Current Behavior

------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: docker.io/library/node:18.18.1-alpine: not found

Possible Solution

When LTS is updated, a corresponding docker image should be promptly created.

Steps to Reproduce

# we run our docker compose command...
docker-compose --env-file .env.jenkins -f ./conf/docker/e2e/docker-compose.yml up --abort-on-container-exit --force-recreate --build

Additional Information

[SimenB]

Yeah, bot isn't picking up the new version for some reason

https://github.com/nodejs/docker-node/actions/runs/6483642231

EDIT: Ah - There's no musl build for version 18.18.1 yet.. It's still building: https://unofficial-builds.nodejs.org/logs/202310111207-v18.18.1/

[mlandisbqs]

I've unblocked us this way - adding an extra check in our LTS check:

async function dockerHubHasLTS(nodeLtsVersion) {
  try {
    await axios.head(`https://hub.docker.com/v2/repositories/library/node/tags/${nodeLtsVersion}`);
  } catch (err) {
    return false;
  }
  return true;
}

[nschonni]

with an assumption that LTS would be supported and promptly available in docker hub. We've never had an issue before but the build is breaking because this version has not been published.

That's not the case (and never has been). There is an automated PR to this repo that is then reviewed by the team, then once that merges, an automated PR to the upstream repo for the Docker hub, which also needs the PRs to be approved.

As @SimenB mentions above, we're waiting for the Unofficial builds to finish the ARM releases, then an automated PR will be created