You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:22:20 UTC
Re: [D] uv issues [superset]
GitHub user dosubot[bot] edited a comment on the discussion: uv issues
<!-- Greeting -->
Hi @jgournet! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
Superset Docker images (starting with v5.0.0 and the current `latest` tag) now use `uv pip` instead of `pip install` for Python dependencies. This change is meant to speed up and simplify dependency management, but it can cause issues if your scripts or workflows expect `pip` or if you end up with an image that doesn't have `uv` installed yet. Discrepancies like this can happen due to image caching, mirror delays, or if a build step that installs `uv` fails or is skipped ([details](https://github.com/apache/superset/blob/2e9939baf253e607a54722b1996baaf625e72133/Dockerfile)).
If you need to support both old and new images, update your install scripts to check for `uv` and fall back to `pip` if it's missing:
```bash
if command -v uv > /dev/null 2>&1; then
uv pip install --no-cache-dir -r "${REQUIREMENTS_LOCAL}"
else
pip install --no-cache-dir -r "${REQUIREMENTS_LOCAL}"
fi
```
([example](https://github.com/apache/superset/issues/32733))
If you’re building your own images or using custom scripts, make sure the base image is fresh and includes the `uv` install step. For older images (4.1.x or earlier), stick with `pip install` ([migration notes](https://github.com/apache/superset/pull/33872)). If you’re running into permission issues with `uv pip`, try running the install as root in your Dockerfile ([workaround](https://github.com/apache/superset/issues/33241)).
If you’re mounting local scripts into the container, make sure they match the version of the image you’re running to avoid mismatches between expected and available tools ([compatibility advice](https://github.com/apache/superset/issues/31510)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=c1975014-c156-43c9-a6c4-9ccb93369548) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33973#discussioncomment-13614212
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org