[Docker] supervisor-exit-event-listener exits with status 127, "not expected"

[kamakazikamikaze]

Debug mode

• I have enabled debug mode
• I have read checked the Common Issues page

Describe the bug

Using Docker image with tag v5.3.0, starting the container results in the supervisord eventlistener "exit_on_any_fatal" to immediately fail, regardless if all other services are running properly. This does not cause the container to exit immediately.

The message: INFO exited: exit_on_any_fatal (exit status 127; not expected)

It appears that the issue is python(2) not being available in the Ubuntu image. The script is run directly and tries to invoke python, which does not exist. python3, however, does, and changing #!/usr/bin/env python to #!/usr/bin/env python3 appears to fix the issue.

Reproduction steps

1. docker pull snipe/snipe-it:v5.3.0
2. Assuming environment is not already set up (MySQL, mail, etc.), set up services as necessary
3. docker run ...
   ...

Expected behavior

exit_on_any_fatal should not exit immediately. A successful launch would show:
INFO success: exit_on_any_fatal entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Screenshots

No response

Snipe-IT Version

5.3.0

Operating System

Ubuntu

Web Server

apache

PHP Version

7.x

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

Docker, fresh install.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[uberbrady]

I'm going to see if I can reproduce this, and then see if the suggested fix seems to fix it.

[Wouter0100]

I had the same issue. The following Dockerfile fixes it.

FROM snipe/snipe-it:v5.3.0

RUN sed -i -e "s/python/python3/" /usr/bin/supervisor-exit-event-listener

[snipe]

@Wouter0100 thanks so much for the update!