Closed hille721 closed 1 year ago
Could be related to different installation directories of ara and gunicorn:
[root@5314d0c4100c ~]# which ara
/usr/local/bin/ara
[root@5314d0c4100c ~]# which gunicorn
/usr/bin/gunicorn
Also just verified, the problem is not only related to 1.7 but more dependent that I updated my base image from Rhel8 to Rhel9 to have Python 3.9.
I already find a easy fix:
Instead of running gunicorn via /usr/bin/gunicorn
, running it via python3 -m gunicorn
. This works.
ah damn, just realized that you also run into that issue a year ago :) https://github.com/ansible-community/ara/issues/406#issue-1330390967
Thus I will close this, but will provide a PR to change the gunicorn command to python3 -m gunicorn
which is probably still a good idea to do it like it, to be safe in the future.
I just wanted to rest the new ara version 1.7.3 but ara is not starting with
ModuleNotFoundError: No module named 'ara'
error.This is the full output when starting ara:
I'm using a own company container image based on Rhel9 and doing basically the same as in https://github.com/ansible-community/ara/blob/master/contrib/container-images/centos-pypi.sh.