run-llama/llama_deploy
1
0
Fork 0
mirror of https://github.com/run-llama/llama_deploy.git synced 2026-08-24 21:01:26 -04:00
Code Issues 37 Packages Projects Releases 10 Wiki Activity

[PR #90] [MERGED] [BUG] Add README reminder to example users to create poetry.lock before first run #257

New Issue
Closed
opened 2026-02-16 01:16:39 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 01:16:39 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/llama_deploy/pull/90
Author: @emekdahl
Created: 7/2/2024
Status: ✅ Merged
Merged: 7/3/2024
Merged by: @jerryjliu

Base: main ← Head: emily/update-llama-agents-docker-example-readme

📝 Commits (2)

  • 1c807b7 add a reminder to docker k8s example users that they must create the poetry.lock file on the first run
  • 300aff9 try again with pre-commit linter

📊 Changes

1 file changed (+51 additions, -41 deletions)

View changed files

📝 examples/docker-kubernetes/README.md (+51 -41)

📄 Description

Observed:

When following the docker k8s example, docker-compose command fails unless we first generate the poetry.lock file. Adding a friendly reminder to others following the example that they need to generate the poetry lock file on the first run.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/llama_deploy/pull/90 **Author:** [@emekdahl](https://github.com/emekdahl) **Created:** 7/2/2024 **Status:** ✅ Merged **Merged:** 7/3/2024 **Merged by:** [@jerryjliu](https://github.com/jerryjliu) **Base:** `main` ← **Head:** `emily/update-llama-agents-docker-example-readme` --- ### 📝 Commits (2) - [`1c807b7`](https://github.com/run-llama/llama_deploy/commit/1c807b7fd5336465b61b378dff14c78c42101242) add a reminder to docker k8s example users that they must create the poetry.lock file on the first run - [`300aff9`](https://github.com/run-llama/llama_deploy/commit/300aff9c1a5df12369605a4741e891e1e7513c88) try again with pre-commit linter ### 📊 Changes **1 file changed** (+51 additions, -41 deletions) <details> <summary>View changed files</summary> 📝 `examples/docker-kubernetes/README.md` (+51 -41) </details> ### 📄 Description Observed: When following the docker k8s example, `docker-compose` command fails unless we first generate the `poetry.lock` file. Adding a friendly reminder to others following the example that they need to generate the poetry lock file on the first run. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 01:16:39 -05:00
yindo closed this issue 2026-02-16 01:16:39 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
P1
P2
bug
documentation
documentation
enhancement
example
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
topic:CLI
topic:SDK
topic:SDK
topic:SDK
topic:apiserver
topic:control_plane
topic:message_queues
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_deploy#257
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?