-
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
Poetry doesn't appear to allow for efficient docker caching when using /src #2549
Comments
Hello @curtiscook, I don't really understand your use-case. But is the fin swimmer |
it's not clear that --no-root supports skipping packages? If it does, it could possibly work? As for my use case -- I want to install the base image with deps into an intermediate container & then install my package into a new container. This increases docker's ability to cache the repo. Currently, it wants to just fail the build. Maybe this should throw a warning w/ a suggestion with --no-root? I was able to work around it, but everything feels very abusive/hacky so I think that there should be more direct support (or documentation) for docker builds |
I'm not familiar with the docker stuff. But that sounds exactly like what |
Duplicate #1132. |
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. |
Feature Request
From: https://python-poetry.org/docs/pyproject/#packages%C2%A0
If your package is included in a subdirectory (i.e. /src), you need to include the path as follows:
The problem is that if you have an actively developed package it's generally more efficient to cache requirements in the base image. This is normally easily accomplished by running
poetry install --no-dev --no-interaction
Unfortunately, if you have a /src directory and implement the package syntax, poetry will fail if the package is not there with the following error
Suggestion/feature request: a flag to skip the packages block when installing the base image
The text was updated successfully, but these errors were encountered: