New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing packags through requirements.txt are not on the path #2000
Comments
My pending pr for the docker refactoring resolves that problem. |
After #1963 have been merged, could you give that |
I think watchtower automatically pulled it. I'm now running into this:
And semaphore no longer starts |
I assume this happens because the |
Looks like I got to add more flags similar to the dockerfile. |
I assume you mean I would advise against as it simply might break the container in unexpected ways, as the flag suggests I'm currently busy with other things, but maybe I can find some time over the weekend to see if I can create a PR that follows a more distro approved way. Maybe just adding |
That's just required because of the restrictions set by alpine devs. The container won't be managed by the alone package manager. Beside that the python deps are only installed in the user space. |
Even if I don't like it, the docker images are using a venev again. |
Thx for fixing the issue and reconsidering. I did not manage to find the time to write a MR. |
I've been trying out the new feature that enable installing python dependencies inside the container. However, something is failing in a weird way.
Some packages seem to be installed on the path others not, specifically httpx, which can be seen in the log:
This makes any script that depends on this fail unless I add:
Although it is a good practice to ensure installation, regardless where the script is running. This behavior is not what I expected. Especially since other packages do seem to work fine.
The text was updated successfully, but these errors were encountered: