IssueRaiser

`poetry install --no-root` with only poetry.lock

<!-- Hi there! Thank you for wanting to make Poetry better. Before you submit this; let's make sure of a few things. Please make sure the following boxes are ticked if they are correct. If not, please try and fulfill these first. --> <!-- Checked checkbox should look like this: [x] --> - [X] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. - [X] I have searched the [documentation](https://poetry.eustace.io/docs/) and believe that my question is not covered. ## Feature Request <!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ --> When doing `poetry install`, both `pyproject.toml` and `poetry.lock` are required. This makes sense as the package itself is installed along with its dependencies. However, this breaks caching in Docker. Let's say I have these lines in docker: ```dockerfile COPY pyproject.toml poetry.lock README.md / RUN poetry install --no-dev ``` (Note how I also need the `README.md` as that is referenced in the `pyproject.toml`) The main problem here is: On every build, I bump the version using `poetry version ...`. This changes the `pyproject.toml` file, therefore breaks the docker caching mechanism. In comparison, with an additional `requirements.txt`, I can do something like: ```dockerfile COPY requirements.txt / RUN pip install -r requirements.txt COPY pyproject.toml poetry.lock README.md / RUN poetry install --no-dev ``` In this case, all the

Posted by emistler on Aug 15, 2019, 9:30 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments

onboarding (Software)

`poetry install --no-root` with only poetry.lock

emistlerAug 15, 2019, 9:30 AM

<!-- Hi there! Thank you for wanting to make Poetry better. Before you submit this; let's make sure of a few things. Please make sure the following boxes are ticked if they are correct. If not, please try and fulfill these first. --> <!-- Checked checkbox should look like this: [x] --> - [X] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. - [X] I have searched the [documentation](https://poetry.eustace.io/docs/) and believe that my question is not covered. ## Feature Request <!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ --> When doing `poetry install`, both `pyproject.toml` and `poetry.lock` are required. This makes sense as the package itself is installed along with its dependencies. However, this breaks caching in Docker. Let's say I have these lines in docker: ```dockerfile COPY pyproject.toml poetry.lock README.md / RUN poetry install --no-dev ``` (Note how I also need the `README.md` as that is referenced in the `pyproject.toml`) The main problem here is: On every build, I bump the version using `poetry version ...`. This changes the `pyproject.toml` file, therefore breaks the docker caching mechanism. In comparison, with an additional `requirements.txt`, I can do something like: ```dockerfile COPY requirements.txt / RUN pip install -r requirements.txt COPY pyproject.toml poetry.lock README.md / RUN poetry install --no-dev ``` In this case, all the

Comments (0)

No comments yet. Start the discussion.

Comment on this issue