Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Not relevant
Are you sure you're not using someone else's docker image?
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug
I tried to start the dev environment using the script scripts/start_dev so I can implement the DNS standalone feature from #2252 but the containers don't start.
It seems it's missing some npm packages which can't be downloaded or found.
yarn install v1.22.19
yarn install v1.22.19
[1/4] Resolving packages...
[1/4] Resolving packages...
[2/4] Fetching packages...
[2/4] Fetching packages...
error https://registry.yarnpkg.com/lodash/-/lodash-4.17.21.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, chmod '/usr/local/share/.cache/yarn/v6/npm-lodash-4.17.21-679591c564c3bffaae8454cf0b3df370c3d6911c-integrity/node_modules/lodash/fp/mergeAllWith.js'"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error https://registry.yarnpkg.com/rimraf/-/rimraf-2.6.3.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "EEXIST: file already exists, mkdir '/usr/local/share/.cache/yarn/v6/npm-rimraf-2.6.3-b2d104fe0d8fb27cf9e0a1cda8262dd3833c6cab-integrity/node_modules/rimraf'"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Uncaught Error: Cannot find module '/app/node_modules/nodemon/bin/nodemon.js'
So the containers all crash except for the database
Nginx Proxy Manager Version
latest git commit d2688cf
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug I tried to start the dev environment using the script
scripts/start_dev
so I can implement the DNS standalone feature from #2252 but the containers don't start.It seems it's missing some npm packages which can't be downloaded or found.
So the containers all crash except for the database
Nginx Proxy Manager Version latest git commit d2688cf
To Reproduce Steps to reproduce the behavior:
./start-dev
docker logs npm_core
as it should show the same error I posted above.Expected behavior Dev environment should start and be accessible via
http://127.0.0.1:3081
Screenshots![crashed container](https://pictshare.net/tiyh5y.png)
Operating System Tested with: