dosubot[bot] commented on issue #33691: URL: https://github.com/apache/superset/issues/33691#issuecomment-2940524521
<!-- Greeting --> Hi @helong001! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team. <!-- Answer --> Your issue is likely caused by two factors: the use of the uv command and the way Superset now manages its Python environment in recent versions. First, the uv command is not present in the official Superset Docker images by default, which means any script using uv pip will fail silently or log an error that may not be visible unless you check the container logs directly. This is a known issue for users trying to install additional Python packages at runtime in containers built from the official image. The recommended workaround is to use the pip executable from the virtual environment Superset uses, which is located at /app/.venv/bin/pip in recent images. For example: ```yaml bootstrapScript: | #!/bin/bash /app/.venv/bin/pip install .[trino] && if [ ! -f ~/bootstrap ]; then echo "Running Superset with uid {{ .Values.runAsUser }}" > ~/bootstrap fi ``` This approach is confirmed to work for installing additional drivers and dependencies in the current containerized setup, as Superset now runs inside a virtual environment at /app/.venv, and packages installed with the system pip will not be visible to Superset itself. If you need to ensure pip is available, you can also run /app/.venv/bin/python -m ensurepip before the install step if you encounter pip not found errors. [Reference](https://github.com/apache/superset/issues/32186) Second, the bootstrapScript is executed at pod startup as part of the default Helm Chart configuration. Unless you have overridden the container command or removed the script mount, it should always run. If ~/bootstrap is missing, it strongly suggests the script failed (likely due to the uv command error) and exited before reaching that line. [Reference](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/helm/superset/values.yaml) After making this change, redeploy your Helm release and check the logs of the Superset pods for any errors during startup. Once the Trino connector is installed in the correct environment, it should appear in the "+ Data" UI dialog. If you continue to have issues, ensure your container user (runAsUser) has sufficient permissions to install Python packages and write to the home directory, and that you have not overridden the default container command or volume mounts in your Helm values. Let me know if you need more details or troubleshooting steps. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/14be77c4-b6af-4542-994e-cb08ce000cdc?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33691) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
