-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BUG] My Dashy Docker container keeps looping and not starting #1617
Comments
Hi
Please share your docker compose file, if the issues persists after changing the port on the host side, but not on the docker side, (like 8090;8080) Also have you tried re-pulling the latest image and rebuilding? (Make sure the conf.yml is mapped as bind volume beforehand.) |
Thank you for the reply :D `version: "3" qbittorrent: sonarr: radarr: prowlarr: bazarr: dashy:
whisperasr: watchtower: autoheal: |
Oh I think I spotted the issue, since dashy V3, the port changed from 80 to 8080, a non-root port. I think the most bottom line of the ports needs to be changed from 80 to 8080. But to be honest I'm a bit confused of why you are running all those services inside a single stack. Here an example for dashy:
|
THANK YOU SO MUCH it worked :D I am still super new to Docker, should I separate all of the containers into their own stacks? I thought the best way to Docker was to just have everything in a single file lol |
Awesome! 🎉 To be honest if you are new to Docker, I'd rather suggest something like portainer, but if you feel comfortable with docker compose, then it's definitely a good choice, as it gives much more freedom. Generally speaking docker containers are used to isolate specific aplications. So generally most people put things like frontend, a database and possibly a backend into the same stack, and then just open up the frontend, this way the backend stays protected and the frontend is accessible. But those are only some ideas/suggestions, feel free to do what you like :) |
Thank you again :D I tried moving it back to using Gluetun so my vpn widget would work, but I keep getting this "Unauthorized" screen :/ maybe I did it wrong though lol, heres what the log says `Unable to start Dashy's Node server Error: listen EADDRINUSE: address already in use 0.0.0.0:8080
code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '0.0.0.0', �` |
Hi
I really think there's still a problem between your vpn or dashy occupying the port. For a vpn I could strongly recommend things like tailscale or twingate, if you're new, you basically install the client on your phone/laptop and on the server , auth with your account and they both get an internal ip where you can reach them. This will then automatically enable the full functionality as if you'd be right at home, without messing with that docker compose that much. |
Thank you :) I think it's because qbittorrent and Dashy both have 8080 now... If there's no way to change one of the ports I may just have to skip the VPN widget I have in Dashy, since if I bind both to Gluetun they clash :/ Thank you for the Tailscale suggestion, but I only use Gluetun with Private Internet Access, I only access my server at home anyway :D |
Nevermind, completely solved it!!!! I accidently put "" around the port, so the formatting broke it, thank yu so much again :) |
Oh awesome 😁 |
Environment
Self-Hosted (Docker)
System
Debian Latest with Portainer 20.10.24 I think
Version
V-3.1.1
Describe the problem
When I start the container it never actually starts, I will attach the logs, I think it keeps looping after building, but i'm not sure lol, it worked before, but I had my storage space full for a few months without realizing it, so I think that I was on an old version and now when it finally updated the looping happens, I tried to delete the entire container and remake it with my compose file, but it still happens, sorry for the bad explanation lol
Additional info
_Dashy_logs.txt
Please tick the boxes
The text was updated successfully, but these errors were encountered: