Question: Why are you installing `postgres-client` and `xdg-utils` in the backend docker image?

[john0isaac]

I'm curious about why you needed to install these two packages for backend postgres-client and xdg-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

	RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
	&& apt-get -y install --no-install-recommends postgresql-client \
	&& apt-get update && apt-get install -y xdg-utils \
	&& apt-get clean -y && rm -rf /var/lib/apt/lists/*

[onestardao]

You’re right to question it — adding postgresql-client and xdg-utils inside a backend image usually means the build is compensating for something upstream.

• postgresql-client is only needed if you expect to run psql inside the container (migrations, manual queries). The app itself doesn’t need it to talk to Postgres.
• xdg-utils is a desktop helper (things like xdg-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?

[pamelafox]

@onestardao Are you a bot? I've seen several of your replies across Azure-samples repos that follow a similar template.

@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...

[onestardao]

Human being but use AI and my own Problem map tools to analyse problem , so I can fix more RAG -related bugs more faster

[pamelafox]

@onestardao Got it, okay! Thanks for clarifying.