docker-compose up fails with exit code 127

docker-compose up fails with exit code 127 in Ubuntu EC2 instance

vulnerablecode_1 | ModuleNotFoundError: No module named 'vulnerablecode.wsgi'
vulnerablecode_1 | [2021-10-01 20:02:11 +0000] [17] [INFO] Worker exiting (pid: 17)
vulnerablecode_1 | [2021-10-01 20:02:11 +0000] [15] [INFO] Shutting down: Master
vulnerablecode_1 | [2021-10-01 20:02:11 +0000] [15] [INFO] Reason: Worker failed to boot.
vulnerablecode_1 | /bin/sh: 1: ./manage.py: not found
vulnerablecode_1 |

vulnerablecode_vulnerablecode_1 exited with code 127

Can someone please look in to this

[pombredanne]

@arun-netsentries Can you provide a bit more details? What exact sequence of commands did you issue?

[list4nestor]

Same issue in my side.
It comes from the "--clear" option that removes files widely, not only static files.

./manage.py collectstatic --no-input --clear

Have a try by removing this option:

./manage.py collectstatic --no-input

[pombredanne]

@list4nestor thank you ++ 🙇
But --clear should not remove files widely... only the ones previously collected.
See https://docs.djangoproject.com/en/3.2/ref/contrib/staticfiles/#collectstatic

@tdruez this was carried from https://github.com/nexB/scancode.io/blob/64d6aa529a875d589e4ffccf4da7eea6190bb6b4/docker-compose.yml#L35 in https://github.com/nexB/vulnerablecode/blob/f9da8362f20219f78860f2bcd4443662f7480e62/docker-compose.yml#L13 ... any specific idea why it would fail here and not there?

[tdruez]

@pombredanne we did not encounter this issue in the ScanCde.io side afaik.

Although looking at the log:

vulnerablecode_1 | ModuleNotFoundError: No module named 'vulnerablecode.wsgi'
vulnerablecode_1 | /bin/sh: 1: ./manage.py: not found

This looks like a setup issue, unrelated with the collectstatic command but rather with the ./manage.py call that fails since the setup is wrong.

[pombredanne]

@arun-netsentries I was not able to reproduce either. Can you provide more details on your setup?
which exact Ubuntu version do you use? Which arch, Python version? Do you have the full logs of the docker-compose run?
Thanks!

[vbisserie]

I reproduce this problem. Here is a possible solution : #569

[pombredanne]

@arun-netsentries I merged the fix from @vbisserie
Can you retest on your side?

[sbs2001]

Closing this for now. @arun-netsentries feel free to open this issue is still present