-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Permission issue when using Poetry 1.5.1, updated from 1.1.13 #8408
Comments
this is almost certainly a bad idea, don't do that - #6398
apparently you are running as a user who does not have permission in that place in the docker image. since you seem to be running as root, I suppose things are marked read-only. This is not a poetry issue, please close. |
The only thing I changed between the two runs was the Poetry version, that's why I posted it here. |
sure, the new poetry probably behaves differently than the old poetry but still the problem you have is one of permissions in your container: which is not a poetry problem |
Maybe I need to move this into discussion? someone else should had a similar issue, don't know where to start, at the end it's running a pip install as the same user as in the 1.1.3, so, the same permissions should be needed, for now, I'll be downgrading. |
the recommended approach is to use a virtual environment, then there'll be no question of trying to make undesirable updates to system packages |
This change fixes an issue where when system environment is used as a destination for wheel installation as a user without access to system site packages, installation fails with permission error. Functionally, this now follows the same behaviour as when a package is installed to user site. Resolves: python-poetry#8408
I had the same issue, but I solved it with the method below.
|
I am getting this error when I do compose-up -d |
For best practices about how to use Poetry in docker please see https://github.com/orgs/python-poetry/discussions/1879 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Have all my repos configured on 1.5.1, read the changelogs and no mention of my issue of similar.
Issue
This is my Dockerfile
if I create the lock file with 1.1.13 and generate the image with the above Dockerfile, everything goes smoothly, Just a warning:
when I create the lock file and run it with 1.5.1 I have this log:
The poetry version is the only thing that changes between a successful and failed build.
Any idea of what could be happening?
Thanks!
The text was updated successfully, but these errors were encountered: