Repository navigation
Question: Why are you installing postgres-client and xdg-utils in the backend docker image? #250
Description
Activity
You’re right to question it — adding
postgresql-clientandxdg-utilsinside a backend image usually means the build is compensating for something upstream.postgresql-clientis only needed if you expect to runpsqlinside the container (migrations, manual queries). The app itself doesn’t need it to talk to Postgres.xdg-utilsis a desktop helper (things likexdg-open), and doesn’t belong in a headless backend unless some script is unexpectedly calling it.
We’ve seen this exact pattern before — image builds that “work” only because they drag in utilities the runtime shouldn’t depend on. In our notes, we classify it as a bootstrap/pre-deploy mis-ordering problem.
If you’d like, I can share the failure-mode checklist we use (16 common cases with fixes). It might help you see where this fits in. Want me to drop that here?
PSBigBig + MiniPS (@onestardao) Are you a bot? I've seen several of your replies across Azure-samples repos that follow a similar template.
John Aziz (@john0isaac) I think the postgresql-client might be useful if you're somehow SSH into the container, though I haven't done that. Most likely they are remnants from devcontainer image and can be removed.
Speaking of bots, we can ask @Copilot to tackle this...
Reacted by John AzizHuman being but use AI and my own Problem map tools to analyse problem , so I can fix more RAG -related bugs more faster
PSBigBig + MiniPS (@onestardao) Got it, okay! Thanks for clarifying.
Reacted by PSBigBig + MiniPS
I'm curious about why you needed to install these two packages for backend
postgres-clientandxdg-utils? Does it not work on container apps unless they are installed or why?rag-postgres-openai-python/src/backend/Dockerfile
Lines 3 to 6 in 23fdf64