Application wont stop even after killing and removing the container.
BugZappa opened this issue · 0 comments
BugZappa commented
Official Instance
- The bug is reproducible on the official hosted instance, or is API-related.
Describe the bug
I can't seem to figure this one out, my Piped instance simply will not stop even after killing and removing piped-frontend, piped-backend, piped-proxy, nginx, watchtower (i think is the name of this application).
I followed the documentation to set Piped up my domain however, didn't have time to set Nginx/SWAG up so i left it with an improper SSL certificate and for the meantime it worked, i come to fix it up today and i cant get this container to shutdown.
To Reproduce
- Follow the "Docker Compose Nginx AIO script" in the documentaion
- Stop, Kill, Remove containers associated
- Still able to access https:// insert.domain/here granted very broken version that infinitely loading
Expected behavior
Container stops and shutdown as expected.
Logs/Errors
Unable to retrieve logs, deleted most of Piped files trying to fix this
Browser, and OS with Version.
Firefox - 131.0.3 (64-bit)
Debian 12 (Bookworm) - Window Manager: KDE Plasma
Additional context
No response