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.

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

👻 force npm9 during image build (#1781) #1787

Merged
merged 1 commit into from
Mar 19, 2024

Commits on Mar 19, 2024

  1. 👻 force npm9 during image build (#1781)

    Ever since the build container we use [1][2] updated to use `npm@10`,
    the image builder github action has encountered a number of problems.
    The first was solved with #1746. The second more random problem has been
    with network connections erroring out when installing dependencies.
    
    To work around the network and nofiles errors:
      1. enforce the use of `npm@9`
      2. pin the Dockerfile base images to specific version tags;
        builder at `:1-88`, and runtime at `:1-93`
    
    Additional solutions:
      - Add the force to `npm@9` directly in the Dockerfile for use in all
        circumstances
      - Find a way to use something like verdaccio to proxy/mirror the npmjs
        repo during the build so npmjs fetches can be pooled across the parallel
        image builds
    
    [1] registry.access.redhat.com/ubi9/nodejs-18:latest
    [2] https://catalog.redhat.com/software/containers/ubi9/nodejs-18/62e8e7ed22d1d3c2dfe2ca01
    
    ---------
    
    Signed-off-by: Scott J Dickerson <[email protected]>
    Signed-off-by: Cherry Picker <[email protected]>
    sjd78 authored and web-flow committed Mar 19, 2024
    Configuration menu
    Copy the full SHA
    7b1331c View commit details
    Browse the repository at this point in the history