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

Problems with in the last update #1031

Closed
Joselito1980 opened this issue Jan 21, 2024 · 1 comment
Closed

Problems with in the last update #1031

Joselito1980 opened this issue Jan 21, 2024 · 1 comment

Comments

@Joselito1980
Copy link

Joselito1980 commented Jan 21, 2024

Hello! I'm updated the dashdot to the last version (V.5.8.0) and now not start. its working in a Synology DSM 7.2.1.
the docker compose it's:


version: "3.9"
services:
dashdot:
container_name: dashdot
image: mauricenino/dashdot
mem_limit: 4g
cpu_shares: 768
security_opt:
- no-new-privileges:true
restart: on-failure:5
volumes:
- /:/mnt/host:ro
ports:
- 7512:3001
privileged: true
environment:
DASHDOT_ENABLE_CPU_TEMPS: true
DASHDOT_OVERRIDE_OS: Synology DSM

Appears this error in the log. Can you help me?

dashdot

date stream content
2024/01/21 08:50:13 stdout $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] ...
2024/01/21 08:50:13 stdout
2024/01/21 08:50:13 stdout Usage Error: Couldn't find a script named "start".
2024/01/21 08:36:38 stdout $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] ...
2024/01/21 08:36:38 stdout
2024/01/21 08:36:38 stdout Usage Error: Couldn't find a script named "start".
2024/01/21 08:34:21 stdout $ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] ...
2024/01/21 08:34:21 stdout
2024/01/21 08:34:21 stdout Usage Error: Couldn't find a script named "start".

@Joselito1980 Joselito1980 changed the title Problems in the last update Problems with in the last update Jan 21, 2024
@Joselito1980
Copy link
Author

I have recreated the container again from "contanier manager in my synology" and it started fine, the problem is now solved. thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant