MichaIng
commented
10 months ago Thanks for reporting. The final actual error that is thrown in a loop is:
AttributeError: '_UnixSelectorEventLoop' object has no attribute '_debug'Strange about it is that this attribute is requested solely within the asyncio module, not by us.
The this error looks more like an attempt to log/warn about another one happened before:
File "/usr/lib/python3.11/asyncio/base_events.py", line 400, in __init__
self._clock_resolution = time.get_clock_info('monotonic').resolution
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [Errno 1] Operation not permittedAs far as I understand the docs about this, it is not even the system clock, but about an internal clock/timer started internally, in this case likely to time the I/O loop iterations: https://docs.python.org/3/library/time.html?highlight=get_clock_info
So no idea how a permissions error can happen in this case. asyncio and time are both Python 3 internal modules, so nothing where 3rd party updates/dependencies should have any effect on.
The issue you linked was about a bare metal motionEye instance on RPi executed via systemd unit, not a Docker container, hence entirely different. You do not need to (or better must not) run the container itself as motion user, especially since that one should not exist on your host system anyway. The container currently requires root permissions, and internally starts motionEye with its internal motion user: https://github.com/motioneye-project/motioneye/blob/dev/docker/entrypoint.sh
The RAEDME indeed needs to be updated for the new version. Your docker run however looks fine. The dirs of the volumes on host end exist?
Ah, although can you try to ship the volume and port options in your docker run? These are defined in the Dockerfile already: https://github.com/motioneye-project/motioneye/blob/dev/docker/Dockerfile#L40-L46
The two volumes are created in the Docker container's directory. I am currently not sure whether the declarations in the Dockerfile just override those you set via CLI, or whether they indeed can conflict.
Kobbe1
Hi,
great project! I thought I give the 0.43 release a try in parallel on my production system (still running buster). I disabled the old 0.42 motioneye service temporarily, and then tried below command:
I am getting several permission errors, so I assumed I am maybe encountering this. Following the 3 steps at the end did not really fix it, but then again I guess I am not actually running as user "motion" (I ran above command under my standard username, I guess I could try to just run the docker as user "motion"?). I am pretty sure this is a permission issue/related to my old install of ME, but I am hoping someone can suggest a reasonable path forward, the old 0.42 install works very well so I am not too keen to mess it up completely - never change a running system.
I guess the docker wiki also needs an update but I think this was said before in some other issue.
Best,
-T