Open sigjas opened 3 years ago
Assuming you are on linux, try
setenforce permissive
Then run your command to start the bot, following with a docker ps to see if the container stays running.
Using raspberry pi OS. Cannot find any tools regarding SELInux.
On Sat, Mar 20, 2021 at 5:36 PM r0b0t2k @.***> wrote:
Assuming you are on linux, try setenforce permissive
Then run your command to start the bot, following with a docker ps to see if the container stays running.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EricJMarti/inventory-hunter/issues/178#issuecomment-803478792, or unsubscribe https://github.com/notifications/unsubscribe-auth/AITIZVJAR2SMNNC74UMWVYDTEUWPDANCNFSM4ZQ3ZKJA .
Using raspberry pi OS. Cannot find any tools regarding SELInux. … On Sat, Mar 20, 2021 at 5:36 PM r0b0t2k @.***> wrote: Assuming you are on linux, try setenforce permissive Then run your command to start the bot, following with a docker ps to see if the container stays running. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#178 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AITIZVJAR2SMNNC74UMWVYDTEUWPDANCNFSM4ZQ3ZKJA .
Oh my apologies, I am using a centos 7 VM on my server I keep at home. And with CentOS, I was getting permission issues when the container would tried to read the configs, so I set selinux to permissive and that fixed my issue. On your PI, see if there is a /var/log/messages, look at the end of the logs right after you run the container. See what you see. I am not familiar with Rasberry PI. Run your container have another terminal going and tail -f /var/log/messages and see what prints to the logs.
E2021-03-20 23:58:26,553 [root] caught exception Traceback (most recent call last): File "/src/run.py", line 57, in main alerters = init_alerters(args) File "/src/alerter/init.py", line 10, in init_alerters return AlerterFactory.create(args) File "/src/alerter/common.py", line 49, in create return cls.create_from_args(args) File "/src/alerter/common.py", line 55, in create_from_args alerter = cls.get_alerter(args.alerter_type) File "/src/alerter/common.py", line 70, in get_alerter
On Sat, Mar 20, 2021 at 7:29 PM r0b0t2k @.***> wrote:
Using raspberry pi OS. Cannot find any tools regarding SELInux. … <#m6607642262783905878> On Sat, Mar 20, 2021 at 5:36 PM r0b0t2k @.***> wrote: Assuming you are on linux, try setenforce permissive Then run your command to start the bot, following with a docker ps to see if the container stays running. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#178 (comment) https://github.com/EricJMarti/inventory-hunter/issues/178#issuecomment-803478792>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AITIZVJAR2SMNNC74UMWVYDTEUWPDANCNFSM4ZQ3ZKJA .
Oh my apologies, I am using a centos 7 VM on my server I keep at home. And with CentOS, I was getting permission issues when the container would tried to read the configs, so I set selinux to permissive and that fixed my issue. On your PI, see if there is a /var/log/messages, look at the end of the logs right after you run the container. See what you see. I am not familiar with Rasberry PI. Run your container have another terminal going and tail -f /var/log/messages and see what prints to the logs.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EricJMarti/inventory-hunter/issues/178#issuecomment-803496402, or unsubscribe https://github.com/notifications/unsubscribe-auth/AITIZVOJDPEYQS5JXX4EJEDTEVDVZANCNFSM4ZQ3ZKJA .
So as I stated above, I am not very familiar with Raspberry PI or its OS. Either some dependency is missing? Perhaps an updated version of python, or some other issue. But I cannot be sure. All I can say is I have had success running the bot in CentOS Linux. Unfortunately those errors only tell me something is missing, some compatibility issue, or permissions elsewhere perhaps.. Only guessing though.
After starting the docker, it stops after a few seconds.