Fix pip freeze logic for #500 - #1461
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2cdbcd8bcf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| MARQO_LOG_LEVEL=`echo "$MARQO_LOG_LEVEL" | tr '[:upper:]' '[:lower:]'` | ||
|
|
||
| if [ "$MARQO_LOG_LEVEL" = "debug" ]; then | ||
| pip freeze |
There was a problem hiding this comment.
In the production image, components/marqo/Dockerfile:54 creates the application .venv with uv sync, which does not seed a pip executable, while line 61 only prepends that environment to PATH. Consequently, this command falls through to the base image's system pip and reports system packages—typically omitting the FastAPI, Uvicorn, and other dependencies actually running Marqo. This matches the CLI documentation: uv venv --help says --seed installs pip, while uv pip freeze --help describes freezing packages installed in an environment. Target the uv-managed environment (for example with uv pip freeze) so the debug diagnostics reflect the running application.
Useful? React with 👍 / 👎.
Fixes #500.