Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Dockfile for V5

Open
#654 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
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, docker, javascript, node.js
Domain
cloud, devops

Research direction

Start with the Dockerfile and the package*.json files used by the shown Azure Container Registry build, then trace the highcharts-export-server install command that invokes install.js. Check the bin/cli.js entry point and run the displayed az acr build command; done means the image builds successfully and the container starts with the requested server command.

Written by the indexing model from the issue text.

Description

I downloaded the V5 and added a Dockerfile under the root directory like below. It threw me the following error when trying to create a docker image and publish it to Azure container registry. Any thoughts?

Dockerfile:
      FROM node:18
      
      WORKDIR /usr/src/app
      
      COPY package*.json ./
      
      RUN npm install
      
      COPY . .
      
      EXPOSE 8080
      
      CMD ["node", "bin/cli.js", "--enableServer", "1", "--port", "8080"]
CLI commands:

az acr build --file Dockerfile --registry 1mapdevacr --image bphighcharts:v5 .

Error:
.
.
Step 4/7 : RUN npm install
 ---> Running in 76a87b1e9f44
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead


> [email protected] install
> node ./install.js

node:internal/modules/cjs/loader:1143
  throw err;
  ^

Error: Cannot find module '/usr/src/app/install.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
    at Module._load (node:internal/modules/cjs/loader:981:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.20.8
npm error code 1
npm error path /usr/src/app
npm error command failed
npm error command sh -c node ./install.js
npm notice
npm notice New major version of npm available! 10.8.2 -> 11.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
npm notice To update run: npm install -g [email protected]
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-04-28T17_46_54_998Z-debug-0.log
The command '/bin/sh -c npm install' returned a non-zero code: 1
2025/04/28 17:47:24 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 1

Run ID: cgnc failed after 1m2s. Error: failed during run, err: exit status 1
Run failed
Dominant language
JavaScript
Stars
368
Forks
265
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 highcharts/node-export-server

All issues in highcharts/node-export-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.