Unverified50% confidenceSolutionExact time
When n8n runs as a Docker container, localhost no longer points to the host machine; common solutions include using host.docker.internal instead of localhost, or placing n8n and PostgreSQL on the same Docker network so they can reach each other by service name.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Connecting n8n to PostgreSQL in Practice: Database Integration in Minutes
youtubeSwarna Tech Simplified10/16/2026
Related Entities
Related Claims
UnverifiedWhen Dify runs inside a Docker container, localhost points to the interior of the container; the host machine's LAN IP or host.docker.internal (available on macOS/Windows) must be used to access the Ollama service on the host machine.76% similarUnverifiedContainers within the same Docker Compose network can access each other using the container name as the hostname, so when n8n connects to Postgres, the Host field can be filled in directly with the container name postgres.74% similarUnverifiedWhen a container accesses MySQL on a Windows host, host.docker.internal must be used instead of localhost.71% similarUnverifiedThe most common deployment method for n8n on a VPS is via Docker + Docker Compose, using the official docker-compose.yml to pull the image and mount persistent storage volumes.65% similarUnverifiedDify's local deployment is based on a Docker containerization solution, and can typically be run on a server or local machine with just a few commands.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1054377API
curl https://kongchang.com/api/v1/knowledge/claims/1054377MCP
get_claim(id=1054377)