Closed OldIMP closed 4 years ago
Changing path
to /
will throw another error: /entrypoint.sh: line 41: pip: command not found
, which I assume is due to the lack of pyinstaller as dependency, which was already listed in requirements.txt. So I assume path: /
is just wrong.
I'm hitting the same exact issue: /entrypoint.sh: line 41: pip: command not found
If I change everything and move it under a src directory, i get /entrypoint.sh: line 47: pyinstaller: command not found
.
Thank you for raising this! I'll look into it
@OldIMP @ThePieBandit
This bug has now been fixed 👍 The issue was stemming from the linux docker containing running within a linux docker container, and then mounting within. After the mount had been complete, the path variables that bash relies on had gone strange.
To fix this, I've put in entrypoint.sh
to specifically look in the pyenv folder for the pip installation.
Furthermore, please find a fork of the example repo with the updated action (https://github.com/JackMcKew/volksschule/tree/master/.github/workflows). The changes neccessary are a pyinstaller path of .
and an artifact path of dist/linux
.
Currently the action looks for the first
.spec
file, so multiple executables will not be created with this action.
@OldIMP
I've just released version 0.1.3 which will let you specify a .spec
file if you have multiple spec files in your directory (like volksschule)
Hope it helps! 😄
I've set up a mini python project w/ everything under the root directory & the standard Python application workflow + pyinstaller-action-linux.
Then I got the following error while running the step Package Application:
I've tried both release 0.1.0 & main. Both had the same error.