blocks|key|1985637|text|您的DATABASE_URL指的是127.0.0.1，它是回送适配器+(更多的这里)。这意味着“连接到我自己”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1985638|当在同一个主机上运行两个应用程序(不使用Docker)时，它们都可以在同一个适配器(也称为localhost)上寻址。|1985639|当在容器中运行这两个应用程序时，它们不像以前一样都在本地主机上。相反，您需要将web容器指向docker0适配器上的db容器的IP地址--+docker-compose为您设置这个地址。|1985640|更改：|1985641|从127.0.0.1到CONTAINER_NAME+(例如db)|1985642|示例：|1985643|DATABASE_URL:+postgres://username:pgpassword@127.0.0.1:5432/mydatabase|code-block|syntax|javascript|1985644|至|1985645|DATABASE_URL:+postgres://username:pgpassword@db:5432/mydatabase|1985646|这要归功于Docker链接：web容器有一个文件(/etc/hosts)，其中有一个指向db容器所在IP的db条目。在试图解析主机名时，这是系统(在本例中是容器)首先要查看的地方。|1985647|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Loopback#Virtual_loopback_interface|1|https://askubuntu.com/questions/247625/what-is-the-loopback-device-and-how-do-i-use-it^0|2|C|H|9|T|5|0|13|2|1|0|19|9|0|13|3|1A|7|1M|2|1Y|E|0|0|1|9|B|E|T|2|0|0|0|0|0|E|3|P|A|18|2|1H|2|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@$9|1F|A|1G|1|1H]|$9|1I|A|1J|1|1K]]|E|$]]|$1|F|3|G|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1X|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1Y|8|@$9|1Z|A|20|B|C]|$9|21|A|22|B|C]|$9|23|A|24|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|25|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|26|8|@]|D|@]|E|$S|T]]|$1|U|3|V|5|6|7|27|8|@]|D|@]|E|$]]|$1|W|3|X|5|R|7|28|8|@]|D|@]|E|$S|T]]|$1|Y|3|Z|5|6|7|29|8|@$9|2A|A|2B|B|C]|$9|2C|A|2D|B|C]|$9|2E|A|2F|B|C]|$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|2I|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]|18|$5|13|14|15|E|$16|19]]]]

Your <code>DATABASE_URL</code> refers to <code>127.0.0.1</code>, which is the <a href="https://en.wikipedia.org/wiki/Loopback#Virtual_loopback_interface" rel="noreferrer">loopback adapter</a> (more <a href="https://askubuntu.com/questions/247625/what-is-the-loopback-device-and-how-do-i-use-it">here</a>). This means &quot;connect to myself&quot;.
When running both applications (without using Docker) on the same host, they are both addressable on the same adapter (also known as <code>localhost</code>).
When running both applications in containers they are not both on localhost as before. Instead you need to point the <code>web</code> container to the <code>db</code> container's IP address on the <code>docker0</code> adapter - which <code>docker-compose</code> sets for you.
Change:
<code>127.0.0.1</code> to <code>CONTAINER_NAME</code> (e.g. <code>db</code>)
Example:
<pre><code>DATABASE_URL: postgres://username:pgpassword@127.0.0.1:5432/mydatabase
</code></pre>
to
<pre><code>DATABASE_URL: postgres://username:pgpassword@db:5432/mydatabase
</code></pre>
This works thanks to Docker links: the <code>web</code> container has a file (<code>/etc/hosts</code>) with a <code>db</code> entry pointing to the IP that the <code>db</code> container is on. This is the first place a system (in this case, the container) will look when trying to resolve hostnames.

blocks|key|825961|text|对于更多的读者，如果您使用的是Docker+desktop+for+Mac，请使用host.docker.internal而不是文档中建议的localhost或127.0.0.1。我遇到了同样的connection+refused...问题。后端api-service无法使用localhost/127.0.0.1连接到postgres。下面是我的docker-compose.yml和环境变量作为引用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|825962|version:+"2"

services:
++api:
++++container_name:+"be"
++++image:+<image_name>:latest
++++ports:
++++++-+"8000:8000"
++++environment:
++++++DB_HOST:+host.docker.internal
++++++DB_USER:+<your_user>
++++++DB_PASS:+<your_pass>
++++networks:+
++++++-+mynw

++db:
++++container_name:+"psql"
++++image:+postgres
++++ports:
++++++-+"5432:5432"
++++environment:
++++++POSTGRES_DB:+<your_postgres_db_name>
++++++POSTGRES_USER:+<your_postgres_user>
++++++POSTGRES_PASS:+<your_postgres_pass>
++++volumes:
++++++-+~/dbdata:/var/lib/postgresql/data
++++networks:
++++++-+mynw|code-block|syntax|javascript|825963|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds^0|F|M|15|K|1Y|9|28|9|2P|L|3F|B|3U|J|4G|8|1S|2|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|F|3|G|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

For further readers, if you're using <code>Docker desktop for Mac</code> use <code>host.docker.internal</code> instead of <code>localhost</code> or <code>127.0.0.1</code> as it's suggested in the <a href="https://docs.docker.com/docker-for-mac/networking/#use-cases-and-workarounds" rel="noreferrer">doc</a>. I came across same <code>connection refused...</code> problem. Backend <code>api-service</code> couldn't connect to <code>postgres</code> using <code>localhost/127.0.0.1</code>. Below is my docker-compose.yml and environment variables as a reference:

<pre><code>version: "2"

services:
 api:
 container_name: "be"
 image: &lt;image_name&gt;:latest
 ports:
 - "8000:8000"
 environment:
 DB_HOST: host.docker.internal
 DB_USER: &lt;your_user&gt;
 DB_PASS: &lt;your_pass&gt;
 networks: 
 - mynw

 db:
 container_name: "psql"
 image: postgres
 ports:
 - "5432:5432"
 environment:
 POSTGRES_DB: &lt;your_postgres_db_name&gt;
 POSTGRES_USER: &lt;your_postgres_user&gt;
 POSTGRES_PASS: &lt;your_postgres_pass&gt;
 volumes:
 - ~/dbdata:/var/lib/postgresql/data
 networks:
 - mynw
</code></pre>

blocks|key|1431775|text|我有两个容器，一个是postgresdb，另一个是调用节点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1431776|我将节点queries.js更改为：|1431777|const+pool+=+new+Pool({
++++user:+'postgres',
++++host:+'localhost',
++++database:+'users',
++++password:+'password',
++++port:+5432,
})|code-block|syntax|javascript|1431778|至|1431779|const+pool+=+new+Pool({
++++user:+'postgres',
++++host:+'postgresdb',
++++database:+'users',
++++password:+'password',
++++port:+5432,
})|1431780|我所要做的就是将主机更改为容器名"postgresdb“，这为我解决了这个问题。我相信这可以做得更好，但我只是在过去的两天里学到了码头撰写/+node.js的东西。|1431781|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I had two containers one called postgresdb, and another call node

I changed my node queries.js from:

<pre class="lang-js prettyprint-override"><code>const pool = new Pool({
 user: 'postgres',
 host: 'localhost',
 database: 'users',
 password: 'password',
 port: 5432,
})
</code></pre>

To

<pre class="lang-js prettyprint-override"><code>const pool = new Pool({
 user: 'postgres',
 host: 'postgresdb',
 database: 'users',
 password: 'password',
 port: 5432,
})
</code></pre>

All I had to do was change the host to my container name ["postgresdb"] and that fixed this for me. I'm sure this can be done better but I just learned docker compose / node.js stuff in the last 2 days.

blocks|key|1431805|text|如果没有其他解决方案对您有效，请考虑手动包装PgPool.connect()，并在收到ECONNREFUSED后重试：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1431806|const+pgPool+=+new+Pool(pgConfig);
const+pgPoolWrapper+=+{
++++async+connect()+{
++++++++for+(let+nRetry+=+1;+;+nRetry%2B%2B)+{
++++++++++++try+{
++++++++++++++++const+client+=+await+pgPool.connect();
++++++++++++++++if+(nRetry+>+1)+{
++++++++++++++++++++console.info('Now+successfully+connected+to+Postgres');
++++++++++++++++}
++++++++++++++++return+client;
++++++++++++}+catch+(e)+{
++++++++++++++++if+(e.toString().includes('ECONNREFUSED')+&&+nRetry+<+5)+{
++++++++++++++++++++console.info('ECONNREFUSED+connecting+to+Postgres,+'+%2B
++++++++++++++++++++++++'maybe+container+is+not+ready+yet,+will+retry+'+%2B+nRetry);
++++++++++++++++++++//+Wait+1+second
++++++++++++++++++++await+new+Promise(resolve+=>+setTimeout(resolve,+1000));
++++++++++++++++}+else+{
++++++++++++++++++++throw+e;
++++++++++++++++}
++++++++++++}
++++++++}
++++}
};|code-block|syntax|javascript|1431807|(关于跟踪，请参见节点-postgres中的本期。)|1431808|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/brianc/node-postgres/issues/1789^0|M|G|0|0|M|2|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

If none of the other solutions worked for you, consider manual wrapping of <code>PgPool.connect()</code> with retry upon having ECONNREFUSED:

<pre><code>const pgPool = new Pool(pgConfig);
const pgPoolWrapper = {
 async connect() {
 for (let nRetry = 1; ; nRetry++) {
 try {
 const client = await pgPool.connect();
 if (nRetry &gt; 1) {
 console.info('Now successfully connected to Postgres');
 }
 return client;
 } catch (e) {
 if (e.toString().includes('ECONNREFUSED') &amp;&amp; nRetry &lt; 5) {
 console.info('ECONNREFUSED connecting to Postgres, ' +
 'maybe container is not ready yet, will retry ' + nRetry);
 // Wait 1 second
 await new Promise(resolve =&gt; setTimeout(resolve, 1000));
 } else {
 throw e;
 }
 }
 }
 }
};
</code></pre>

(See <a href="https://github.com/brianc/node-postgres/issues/1789" rel="nofollow noreferrer">this issue</a> in node-postgres for tracking.)

blocks|key|1431832|text|我在这里对处理这件事做了个小小的修改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1431833|正如安迪在他的回答中所说的。|offset|length|1431834|“您需要将web容器指向db容器的|unordered-list-item|style|CODE|1431835|并考虑到关于船坞-合成链接的正式文档|1431836|“为了使服务能够通信，不需要链接--默认情况下，任何服务都可以以该服务的名称到达任何其他服务。”|1431837|因此，您可以以这样的方式保存您的docker_compose.yml：|1431838|docker_compose.yml|BOLD|1431839|version:+"3"
services:
++++web:
++++++image:+node
++++++command:+npm+start
++++++ports:
+++++++++-+"8000:4242"
++++++#+links:
++++++#+++-+db
++++++working_dir:+/src
++++++environment:
++++++++SEQ_DB:+mydatabase
++++++++SEQ_USER:+username
++++++++SEQ_PW:+pgpassword
++++++++PORT:+4242
++++++++#+DATABASE_URL:+postgres://username:pgpassword@127.0.0.1:5432/mydatabase
++++++++DATABASE_URL:+"postgres://username:pgpassword@db:5432/mydatabase"
++++++volumes:
++++++++++-+./:/src
++++db:
++++++image:+postgres
++++++ports:
++++++++++-+"5432:5432"
++++++environment:
++++++++POSTGRES_USER:+username
++++++++POSTGRES_PASSWORD:+pgpassword|code-block|syntax|javascript|1431840|但这是一种很酷的方式，在我们编码的时候变得冗长。所以，你的方法很好。|1431841|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/114770/andy|1|https://docs.docker.com/compose/compose-file/compose-file-v2/#links^0|0|2|2|0|0|5|3|C|2|0|6|7|1|0|0|0|0|I|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|F|3|G|5|H|7|1F|8|@$D|1G|E|1H|I|J]|$D|1I|E|1J|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1K|8|@]|9|@$D|1L|E|1M|1|1N]]|A|$]]|$1|M|3|N|5|H|7|1O|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1Q|8|@$D|1R|E|1S|I|S]]|9|@]|A|$]]|$1|T|3|U|5|V|7|1T|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|1U|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

I am here with a tiny modification about handle this.

As <a href="https://stackoverflow.com/users/114770/andy">Andy</a> say in him response. 

<ul>
<li>"you need to point the <code>web</code> container to the <code>db</code> container's"</li>
</ul>

And taking in consideration the official documentation about <a href="https://docs.docker.com/compose/compose-file/compose-file-v2/#links" rel="nofollow noreferrer">docker-compose link's</a>

<ul>
<li>"Links are not required to enable services to communicate - by default, any service can reach any other service at that service’s name."</li>
</ul>

Because of that, you can keep your docker_compose.yml in this way:

docker_compose.yml

<pre><code>version: "3"
services:
 web:
 image: node
 command: npm start
 ports:
 - "8000:4242"
 # links:
 # - db
 working_dir: /src
 environment:
 SEQ_DB: mydatabase
 SEQ_USER: username
 SEQ_PW: pgpassword
 PORT: 4242
 # DATABASE_URL: postgres://username:pgpassword@127.0.0.1:5432/mydatabase
 DATABASE_URL: "postgres://username:pgpassword@db:5432/mydatabase"
 volumes:
 - ./:/src
 db:
 image: postgres
 ports:
 - "5432:5432"
 environment:
 POSTGRES_USER: username
 POSTGRES_PASSWORD: pgpassword
</code></pre>

But it is a kinda cool way to be verbose while we are coding. So, your approach it is nice.

blocks|key|1985775|text|正如前面提到的，这里。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1985776|每个容器现在都可以查找主机名web或db，并返回相应容器的IP地址。例如，web的应用程序代码可以连接到postgres://db:5432并开始使用Postgres数据库。注意HOST_PORT和CONTAINER_PORT之间的区别是很重要的。在上面的示例中，对于db，HOST_PORT是8001，容器端口是5432+(postgres默认值)。网络服务到服务的通信使用CONTAINER_PORT.当定义HOST_PORT时，服务也可以在群集之外访问。在web容器中，到db的连接字符串看起来像postgres://db:5432，从主机上看，连接字符串看起来像postgres://{DOCKER_IP}:8001。|blockquote|style|CODE|1985777|所以DATABASE_URL应该是postgres://username:pgpassword@db:5432/mydatabase|1985778|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/compose/networking/^0|8|2|0|0|E|3|I|2|11|3|1G|I|2H|9|2R|E|3Q|2|3T|9|43|4|4D|4|58|E|5Q|9|6F|3|6N|2|6Z|I|7X|R|0|2|C|H|1D|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@$A|X|B|Y|G|H]|$A|Z|B|10|G|H]|$A|11|B|12|G|H]|$A|13|B|14|G|H]|$A|15|B|16|G|H]|$A|17|B|18|G|H]|$A|19|B|1A|G|H]|$A|1B|B|1C|G|H]|$A|1D|B|1E|G|H]|$A|1F|B|1G|G|H]|$A|1H|B|1I|G|H]|$A|1J|B|1K|G|H]|$A|1L|B|1M|G|H]|$A|1N|B|1O|G|H]|$A|1P|B|1Q|G|H]|$A|1R|B|1S|G|H]]|9|@]|C|$]]|$1|I|3|J|5|6|7|1T|8|@$A|1U|B|1V|G|H]|$A|1W|B|1X|G|H]]|9|@]|C|$]]|$1|K|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

As mentioned <a href="https://docs.docker.com/compose/networking/" rel="nofollow noreferrer">here</a>.
<blockquote>
Each container can now look up the hostname <code>web</code> or <code>db</code> and get back the appropriate container’s IP address. For example, <code>web</code>’s application code could connect to the URL <code>postgres://db:5432</code> and start using the Postgres database.
</blockquote>
<blockquote>
It is important to note the distinction between <code>HOST_PORT</code> and <code>CONTAINER_PORT</code>. In the above example, for <code>db</code>, the <code>HOST_PORT</code> is <code>8001</code> and the container port is <code>5432</code> (postgres default). Networked service-to-service communication uses the <code>CONTAINER_PORT</code>. When <code>HOST_PORT</code> is defined, the service is accessible outside the swarm as well.
</blockquote>
<blockquote>
Within the <code>web</code> container, your connection string to <code>db</code> would look like <code>postgres://db:5432</code>, and from the host machine, the connection string would look like <code>postgres://{DOCKER_IP}:8001</code>.
</blockquote>
So <code>DATABASE_URL</code> should be <code>postgres://username:pgpassword@db:5432/mydatabase</code>

I'm building an app running on NodeJS using postgresql.
I'm using SequelizeJS as ORM.
To avoid using real postgres daemon and having nodejs on my own device, i'm using containers with docker-compose.

when I run <code>docker-compose up</code>
it starts the pg database

<pre><code>database system is ready to accept connections
</code></pre>

and the nodejs server.
but the server can't connect to database.

<pre><code>Error: connect ECONNREFUSED 127.0.01:5432
</code></pre>

If I try to run the server without using containers (with real nodejs and postgresd on my machine) it works.

But I want it to work correctly with containers. I don't understand what i'm doing wrong.

here is the <code>docker-compose.yml</code> file

<pre><code>web:
 image: node
 command: npm start
 ports:
 - "8000:4242"
 links:
 - db
 working_dir: /src
 environment:
 SEQ_DB: mydatabase
 SEQ_USER: username
 SEQ_PW: pgpassword
 PORT: 4242
 DATABASE_URL: postgres://username:pgpassword@127.0.0.1:5432/mydatabase
 volumes:
 - ./:/src
db:
 image: postgres
 ports:
 - "5432:5432"
 environment:
 POSTGRES_USER: username
 POSTGRES_PASSWORD: pgpassword
</code></pre>

Could someone help me please?

(someone who likes docker :) )

ECONNREFUSED for Postgres on nodeJS with dockers

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在使用postgresql在NodeJS上构建一个应用程序。我使用SequelizeJS作为ORM。为了避免使用真正的postgres守护进程，并在我自己的设备上使用nodejs，我使用了带有docker编写的容器。当我运行docker-compose up时，它将启动pg数据库database system is...

问基于码头的nodeJS邮递员系统
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问基于码头的nodeJS邮递员系统EN