dashy
dashy copied to clipboard
[BUG] Dashboard does not start
Environment
Self-Hosted (Docker)
System
Docker version 20.10.18
Version
2.1.1
Describe the problem
I can't start the Dashy container of the latest version (2.1.1), it loads Dashy but at the end the dashboard doesn't appear, it hangs. I pass the log.
Additional info
today at 13:50:58- Building for production...
today at 13:50:58 WARN A new version of sass-loader is available. Please upgrade for best experience.
today at 13:51:03node:internal/errors:464
today at 13:51:03 ErrorCaptureStackTrace(err);
today at 13:51:03 ^
today at 13:51:03
today at 13:51:03Error: getaddrinfo EAI_AGAIN Dashy
today at 13:51:03 at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26) {
today at 13:51:03 errno: -3001,
today at 13:51:03 code: 'EAI_AGAIN',
today at 13:51:03 syscall: 'getaddrinfo',
today at 13:51:03 hostname: 'Dashy'
today at 13:51:03}
today at 13:51:03error Command failed with exit code 1.
today at 13:51:03info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
today at 13:51:03ERROR: "start" exited with 1.
today at 13:51:03error Command failed with exit code 1.
Please tick the boxes
- You have explained the issue clearly, and included all relevant info
- You are using a supported version of Dashy
- You've checked that this issue hasn't already been raised
- You've checked the docs and troubleshooting guide
- You agree to the code of conduct
Fast, reliable, and secure dependency management.
Probably related with #877, please test with master branch Dockerfile to build the image
Ok, I'll give it a try. Thanks
Probably related with #877, please test with master branch Dockerfile to build the image
My beautiful Dashy doesn't start anymore...but I'm not able to edit the dockerfile, just waiting for a new release of the container...I hope that will fix it.
This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.
This issue was automatically closed because it has been stalled for over 6 weeks with no activity.