It’s happened to me several times:
I try to stop a running container and it fails to stop and it can’t be force-stopped or killed either.
When this happens, Container Station itself also cannot be stopped, and finally, trying to restart the NAS fails. It is totally unacceptable that a single runaway container can cause the whole NAS to become unresponsive. The whole purpose of container technology is to isolate and protect the NAS OS from malfunctioning containers. In case of QNAP, this seems to be a known issue. Their container engine implementation isn’t robust enough.
Just for the records; Of course I tried all possible ways to stop, cancel, reboot and kill from CLI, but to no avail. The only and final solution was hard reset.
Never had this happen to me …what container did this happen on?
Home Assistant v2025.5.1
Im on 2025.5.3 with no issue with crashes
Can you access in ssh?
if yes docker “docker ps” then “stop <container_name>”
dump the logs here
“cat /var/log/log_sys.log” and "cat /var/log/docker.log " and or “docker logs <container_name>”
Can’t help without logs.
As I already said; I tried all possible (and impossible) CLI commands, but to no avail.
Did you open a ticket so QNAP can take a look at it ?
Your posts sounds like this container station issue is widely discussed, but that is the first time I have heard of it (Unless this is not publicly discussed on the usual reddit/community/etc places)
I had to har reset the NAS to get back up.
It was ChatGPT that informed me that this was a known problem with CS. And that matches well with my own experience. This is not the first time it has happened to me.
Not doubting you have the issue, but ChatGPT is a very bad source as it’s known to make up facts on the spot (hallucination)… As long as I don’t see these issues anywhere else, where would that info for ChatGPT come from ? (and these LLMs are often many many months behind when it comes to up to date info)
You never said if you opened a ticket or not.
1 Like