-
Notifications
You must be signed in to change notification settings - Fork 102
Machinery does not run in arm/v7 dockerimage #219
Comments
Hey @GittyDan , running in the same issue. Did You find a sollution. I looked into the docker department and didnt find the issue issued there. I assume you solved it. Can You give a hint if so ? Many greetings |
Thanks for reporting all, could one of you share the machinery logs? |
I am not sure if these are the Machinery logs, but here are the logs from the System view, hope it helps.
|
Are you connecting a Raspberry Pi camera? |
No, I want to use an external IP camera with an RTSP stream |
Then you should change it to IPCamera. Currently it is set to Raspberry Pi camera.
|
Ah okay. I see. In my case, I wanted to use an IP camera, but because it was still set to RaspiCamera (That was not connected) it failed. How I fixed it:
Thanks for the help @cedricve. Much appreciated. :) |
No worries we are adding an autodetect or warning in the next major release 3.0. So it is more obvious. |
I tried the kerberos/kerberos:latest dockerimages on two architectures. both times i started a blank container.
Docker for Windows: linux/amd64
Qnap TS-431P2 NAS: linux/arm/v7
Here the console output of the container:
The machinery is exiting all the time.
Edit: Sry, wrong repo. must be kerberos-docker-repo.
The text was updated successfully, but these errors were encountered: