Zoneminder container starts with state STOPPED about zoneminder-base HOT 16 OPEN

That's a nice clue! Then the problem is not with Arch itself but the fact that Arch uses always the latest software versions.

I guess this is an incompatibility with the s6 version with the new docker version. I'll do some research on this an come up with a PR if I find a solution.

from zoneminder-base.

Hi all, I think the issue is caused by insufficent linux capabilities - changing the user running 'zmpkg.pl start' from www-data to root allows the socket to open (in /etc/services.d/zoneminder/run).

from zoneminder-base.

I am noticing this too... Is the zmpkg.pl start missing from the /init when the container starts?

from zoneminder-base.

I am noticing this too... Is the zmpkg.pl start missing from the /init when the container starts?

No, it's not missing. The error messages comes precisely from executing "zmpkg.pl start" in the s6 init

I've done alot of debug and I really can't understand why this happens.

from zoneminder-base.

Can you provide some more info such as os, docker compose files, env file, etc?

from zoneminder-base.

The only changes I made from the initial git clone was just the timezone and exposed port:

.env:
+TZ=America/New_York

docker-compose.yml:
+9086:80

Also, my base server is x86_64 Linux 6.1.13-1-lts... I use arch btw :)

Docker version 23.0.1, build a5ee5b1dfc
Docker Compose version 2.16.0

from zoneminder-base.

Honestly none of that info gives me enough information to reproduce what exactly you did and if that's unable to be done, there's no way of determining the cause other than pure speculation. As you can see, the image boots up just fine in CI and I believe many others use it without any issues. I would have to believe you must be doing something special or out of the ordinary to cause this issue.

from zoneminder-base.

I think this is an issue related with Arch, as I'm running it as well. I tried running it on Debian and it worked.
I really don't understand what's causing this.

from zoneminder-base.

+1

also on arch, and the problems seems to come from one of the updates of the last month(s). Zoneminder runned perfectly for months, then i recently installed long waited updates ( my internet was realy bad up until two days ago, so i didn't realy update often) and then it stoped working.

at least i have a work around, thanks to @tokenize47 because of the post on the zoneminder forum i found prior to this issue here.

from zoneminder-base.

The problem seems to only happen with Docker 23.0.1.

Docker 20.10.23 seem to work fine. So i think it will be something that has changed from docker 20.10.23 to docker 23.0.1.

Downgrading to docker 20.10.23 and rebooting (somehow restarting the service is not enough) and zoneminder is running normaly.

from zoneminder-base.

Any updates on this?

from zoneminder-base.

Problem persists with Docker 24.0.2

i have no clue how this problem could be solved.

from zoneminder-base.

This could be the same problem as:
#50

Try upgrading from "docker-compose" to "docker compose".

from zoneminder-base.

Thanks for the hint.

But I don't think it is related (at least in my case).

I deploy with portainer, to a 3 cluster docker swarm (although this stack is locked to my NAS because of the hard drives)

from zoneminder-base.

can confirm.

as a quick test i updated to docker 24.0.5 and replaced the file inside the container with one where www-run is replaced with root.

Zoneminder starts without problems now. so at least we now know why it allways starts stopped.

thx for the update @kondas

from zoneminder-base.