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
Update running viewtube in a "crash" loop #2559
Comments
Hi, thank you for opening this issue. Would you be able to post your current docker conpose file? |
And maybe you have the log messages of the ViewTube container? I am running watchtower as well for the production setup (https://viewtube.io) and it has worked for me, so I am curious to see what could be causing this issue. |
Thanks for the fast acknowlegdement. Unfortunatelly, I restarted whole stack again to make FE go up, without saving logs, my bad sorry :( I'll save it on next update and add it...
|
I can't seem to reproduce it :( I will leave this issue open, and hopefully it will work for the next upgrade, or maybe you get a useful log message. |
let's do so, I will save logs next time |
Ok seems I got it again: ViewTube logs:
Although Redis didn't update (fixed to
etc.. Can it be that previous viewtube went down "dirty" which brought Redis above visible error loop and didn't allow it to accept connections from new instance? Stopping whole stack and starting it again, resolved the issue (like previous times). Let me know if you need more info. |
Could you send the docker compose part for redis and mongodb? |
Missed this until now somehow, sorry for that.. here follows the important part of compose.yaml
of course In all honesty, I didn't notice previously described issue since my last comment. I will observe this again, and close if nothing similar occurs for the next update or two. Cheers |
Describe the Bug
Setup/selfhosting on linux with portainer via example docker-compose (portainer stack), and after updates viewtube can't connect to redis and goes into crashloop.
Used compose.yaml in portainer stack has the
depends_on:
section with two dependee containers properly listed.However when new image for viewtube appear and just that container restarts to use new image but redis and mongodb are still running from previous stack instance, viewtube can't start properly.
Steps to Reproduce the Bug
Expected Behaviour
after image update of viewtube, container can properly start and connect to already running support containers
Device Info
Linux with docker, portainer and watchtower
Additional Context
Observed this after every viewtube image update.
cc: @moisout
The text was updated successfully, but these errors were encountered: