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

Website container is not starting for some members #430

Open
SPDonaghy opened this issue Aug 30, 2024 · 0 comments
Open

Website container is not starting for some members #430

SPDonaghy opened this issue Aug 30, 2024 · 0 comments
Assignees
Labels
bug Something isn't working infrastructure web Website team

Comments

@SPDonaghy
Copy link
Contributor

Description

Expected Behavior

Website container starts with no issues and the website is available at http://localhost:3005/

Actual Behavior

website container fails to start with the following error log

0 verbose cli /home/fyang151/.nvm/versions/node/v20.15.1/bin/node /home/fyang151/.nvm/versions/node/v20.15.1/bin/npm
1 info using [email protected]
2 info using [email protected]
3 silly config:load:file:/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/npmrc
4 silly config:load:file:/home/fyang151/sailbot_workspace/src/.npmrc
5 silly config:load:file:/home/fyang151/.npmrc
6 silly config:load:file:/home/fyang151/.nvm/versions/node/v20.15.1/etc/npmrc
7 verbose title npm install
8 verbose argv "install"
9 verbose logfile logs-max:10 dir:/home/fyang151/.npm/_logs/2024-08-28T19_42_18_475Z-
10 verbose logfile /home/fyang151/.npm/_logs/2024-08-28T19_42_18_475Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly idealTree buildDeps
14 silly reify moves {}
15 verbose stack Error: Could not read package.json: Error: ENOENT: no such file or directory, open '/home/fyang151/sailbot_workspace/src/package.json'
15 verbose stack     at async open (node:internal/fs/promises:639:25)
15 verbose stack     at async readFile (node:internal/fs/promises:1249:14)
15 verbose stack     at async PackageJson.load (/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:129:31)
15 verbose stack     at async PackageJson.normalize (/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:115:5)
15 verbose stack     at async runScript (/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:11:28)
15 verbose stack     at async Install.exec (/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/lib/commands/install.js:163:9)
15 verbose stack     at async module.exports (/home/fyang151/.nvm/versions/node/v20.15.1/lib/node_modules/npm/lib/cli/entry.js:74:5)
16 verbose cwd /home/fyang151/sailbot_workspace/src
17 verbose Linux 5.15.153.1-microsoft-standard-WSL2
18 verbose node v20.15.1
19 verbose npm  v10.7.0
20 error code ENOENT
21 error syscall open
22 error path /home/fyang151/sailbot_workspace/src/package.json
23 error errno -2
24 error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/home/fyang151/sailbot_workspace/src/package.json'
25 error enoent This is related to npm not being able to find a file.
25 error enoent
26 verbose exit -2
27 verbose code -2
28 error A complete log of this run can be found in: /home/fyang151/.npm/_logs/2024-08-28T19_42_18_475Z-debug-0.log

Steps to Reproduce

Unknown at this time.

Relevant Code

Potential Solutions

Resources

@SPDonaghy SPDonaghy added the bug Something isn't working label Aug 30, 2024
@SPDonaghy SPDonaghy self-assigned this Aug 30, 2024
@github-project-automation github-project-automation bot moved this to Backlog in SOFT Project Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working infrastructure web Website team
Projects
Status: Backlog
Development

No branches or pull requests

1 participant