What is correct way to connect web-only and data Discourse docker containers? There is note about DISCOURSE_HOST_IP in readme, but how should we specify that variable in container config yml file? Can we just link that images together?

What you do is expose the port on the host, then you can easily connect to it from any container. The “expose” section in the yml takes care of it: expose: - "5432:5432" - "6379:6379" - "2221:22" Then all you need to do is plug in local machine ip here: samples/web_only.yml mas…

Hmm.. but what is YOUR_IP_ADDRESS here? The external IP of the server (I guess not), or the variable DISCOURSE_HOST_IP? I want to use web_only.yml and have a central redis and postgresql service on my server running.

It really depends on how you set up your server. Try running ifconfig I think you should be able to use docker0 for this. 172.17.42.1

Last question (I think): what to use for DISCOURSE_DB_SOCKET? It should point to the socket of the host, but will it have access to it? And why set a pasword if not setting a user variable?

Linking containers

Product Support Self-hosting

Sander78 (Sander Datema) 31 Março , 2014 07:14 5

You’re right, it’s that IP address. On both sites. Thanks.

Tópico		Respostas	Vistas
Linking containers for a multiple container setup Self-hosting	2	10398	9 Janeiro , 2015
Use multiple Docker containers without exposing ports Sysadmins docker , how-to , advanced-setup	10	29060	2 Junho , 2017
Docker setup for App and Redis Self-hosting docker	6	4015	6 Abril , 2015
Using Discourse with external PostgreSQL and Redis Self-hosting docker , advanced-setup	1	1272	26 Outubro , 2023
Connect to database and redis on a docker host using sockets Self-hosting postgres	1	144	31 Março , 2025

Linking containers

Related topics