Hariprasath-0018 commented on issue #37560:
URL: https://github.com/apache/superset/issues/37560#issuecomment-3822829623
Hi Dosu,
Please find the details below regarding the pyodbc issue:
1.
*Dockerfile changes*
I updated my Dockerfile as shown below:
FROM apache/superset:latest
USER root
RUN uv pip install --no-cache-dir pyodbc
USER superset
2.
*Installed packages verification*
Since the full package list is lengthy, I am sharing only the packages
starting with the letter *“p”*. I do not see pyodbc in the list:
packaging 25.0
pandas 2.1.4
pandas-gbq 0.19.1
parameterized 0.9.0
paramiko 3.5.1
parsedatetime 2.6
pathable 0.4.3
pgsanity 0.2.9
pillow 11.3.0
pip 25.1.1
platformdirs 4.3.8
pluggy 1.5.0
ply 3.11
polyline 2.0.2
pre-commit 4.1.0
prison 0.2.1
progress 1.6
prompt-toolkit 3.0.51
prophet 1.2.0
proto-plus 1.25.0
protobuf 4.25.5
psutil 6.1.0
psycopg2-binary 2.9.6
pyarrow 16.1.0
pyasn1 0.6.1
pyasn1-modules 0.4.2
pycparser 2.22
pydata-google-auth 1.9.0
pydruid 0.6.9
pyfakefs 5.3.5
pygments 2.19.1
pyhive 0.7.0
pyinstrument 4.4.0
pyjwt 2.10.1
pylint 3.3.7
pynacl 1.5.0
pyopenssl 25.1.0
pyparsing 3.2.3
pysocks 1.7.1
pytest 7.4.4
pytest-cov 6.0.0
pytest-mock 3.10.0
python-dateutil 2.9.0.post0
python-dotenv 1.1.0
python-geohash 0.8.5
python-ldap 3.4.4
pytz 2025.2
pyxlsb 1.0.10
pyyaml 6.0.2
3.
*Docker build logs*
I did not observe any errors or warnings during the Docker build
process, especially at the uv pip install pyodbc step.
4.
*Image rebuild confirmation*
I rebuilt the Docker image using the following command:
docker compose -f docker-compose-image-tag.yml build --no-cache
Despite these steps, the pyodbc module is still not available inside the
container.
Please let me know if I am missing any dependency or if additional
configuration is required.
Thanks,
Hariprasath N
On Fri, 30 Jan 2026 at 15:11, dosubot[bot] ***@***.***> wrote:
> *dosubot[bot]* left a comment (apache/superset#37560)
> <https://github.com/apache/superset/issues/37560#issuecomment-3822789519>
>
> This persistent error usually means pyodbc still isn’t installed in the
> Python environment Superset actually uses at runtime. To help you debug,
> could you please:
>
> 1. Share the relevant part of your Dockerfile (especially the lines
> where you install pyodbc, switch users, or do anything with virtual
> environments).
> 2. Run uv pip list and/or pip freeze inside your running Superset
> container and paste the output here.
> 3. Let me know if you saw any errors or warnings during the Docker
> build, especially at the uv pip install pyodbc step.
> 4. Confirm you rebuilt your Docker image with --no-cache or --force-rm.
>
> Also, double-check that your Dockerfile does not recreate the virtual
> environment (e.g., with python3 -m venv /app/.venv), as this will break
> package visibility even if you use uv pip install.
>
> Once I have this info, I can help you pinpoint exactly what’s going wrong
> and get pyodbc working in your container.
>
> *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.*
> ------------------------------
>
> How did I do? Good
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=great_response>
> | Irrelevant
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=irrelevant_answer>
> | Incorrect
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=incorrect_sources>
> | Verbose
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=too_verbose>
> | Hallucination
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=hallucination>
> | Report 🐛
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=bug_report>
> | Other
>
<https://app.dosu.dev/response-feedback/5faf72b1-f5a6-4a3c-b244-90d9a917cc4d?feedback_type=other>
>
> [image: Chat with Dosu]
>
<https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github>
> [image: Open in Cursor]
>
<https://cursor.com/link/prompt?text=This%20persistent%20error%20usually%20means%20pyodbc%20still%20isn%E2%80%99t%20installed%20in%20the%20Python%20environment%20Superset%20actually%20uses%20at%20runtime.%20To%20help%20you%20debug%2C%20could%20you%20please%3A%0A%0A1.%20Share%20the%20relevant%20part%20of%20your%20Dockerfile%20%28especially%20the%20lines%20where%20you%20install%20pyodbc%2C%20switch%20users%2C%20or%20do%20anything%20with%20virtual%20environments%29.%0A2.%20Run%20uv%20pip%20list%20and/or%20pip%20freeze%20inside%20your%20running%20Superset%20container%20and%20paste%20the%20output%20here.%0A3.%20Let%20me%20know%20if%20you%20saw%20any%20errors%20or%20warnings%20during%20the%20Docker%20build%2C%20especially%20at%20the%20uv%20pip%20install%20pyodbc%20step.%0A4.%20Confirm%20you%20rebuilt%20your%20Docker%20image%20with%20--no-cache%20or%20--force-rm.%0A%0AAlso%2C%20double-check%20that%20your%20Dockerfile%20does%20not%20recreate%20the%20virtual%20environment%20%28e.g.%2C%20
with%20python3%20-m%20venv%20/app/.venv%29%2C%20as%20this%20will%20break%20package%20visibility%20even%20if%20you%20use%20uv%20pip%20install.%0A%0AOnce%20I%20have%20this%20info%2C%20I%20can%20help%20you%20pinpoint%20exactly%20what%E2%80%99s%20going%20wrong%20and%20get%20pyodbc%20working%20in%20your%20container.>
> [image: Join Discord] <https://go.dosu.dev/discord-bot> [image: Share on
> X]
>
<https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/37560>
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/superset/issues/37560#issuecomment-3822789519>,
> or unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/BCNYORW6BE7QTEQHZR37AZT4JMRMJAVCNFSM6AAAAACTMZQOACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRSG44DSNJRHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
--
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]
