I am installing Docker on a host where all applications are already containerised including the main smtp server. When I try and relay mail from discourse to this smtp server it fails because the server cannot do a reverse lookup on the Discourse server IP. This works fine with my other containers …

We don’t use Docker compose (in any of the many forms it has taken over the years), so we’re not going to be able to translate an isolated snippet of its config into anything useful. What are you actually trying to achieve, in general terms? rDNS isn’t usually Docker’s concern, and it’s weird that…

Ok, I will simplify the question. Docker container_a with a service configured to use Docker network_a needs to talk to container_b (discourse) using the internal Docker network. With docker compose I would simply add network_a to the networks configured for the service in container_b and set it as…

What docker command line would you run to make what you want to have happen, happen?

None, I use docker-compose and the yml config example posted in the original question. I have tried using network args with launcher but this did not work ./launcher start my_forum --docker-args "–network mail_server"

Note the hypothetical implied by the use of the word “would” in my question. I’m not asking what docker command line you do run, I’m asking what you would run, were you to eschew the use of docker-compose and instead implement the same configuration without it. It should be at least theoretically …

OK Matt, thanks for your help. I will eventually figure it out for myself and update this topic with the answer for any other poor unfortunate souls seeking support like myself :slight_smile:

Does docker network connect mail_server [discourse_container_id] work? Obviously not ideal because it’ll need to be done again after each bootstrap, but should work until you have a full solution.

Just tried that Cameron, and yes it works. I think the syntax in my launcher args could be wrong, I am just checking it now.

Trying to add the network via the launcher args doesn’t seem to work at all. Manually connecting the network with network connect works but doesn’t register the host name of the discourse service with dockers name resolution system so the mail server hostname lookup (ping my_forum) fails. So I am b…

Does it work if you pass --alias my_forum to the network connect command? I just found this too: [Bild] Starting Discourse on a Specific Docker Network support It looks like I can specify docker args in web_only.yml though, do you know the syntax for that? Edit: Okay the…

Benutzerdefinierte Docker-Netzwerkkonfiguration – Container-zu-Container-Kommunikation

Unterstützung Installation

Cameron_D (Cameron:D) 6. April 2018 um 10:57 11

Does it work if you pass --alias my_forum to the network connect command?

I just found this too:

(I’ll be trying to get my Discourse instance onto an internal network soon, so I’m interested to see what you get working)

Thema		Antworten	Aufrufe
Set custom docker network in container/app.yml Self-hosting	2	1262	27. Dezember 2021
Starting Discourse on a Specific Docker Network Support	10	3818	2. März 2022
Using Discourse with external PostgreSQL and Redis Self-hosting docker , advanced-setup	2	1082	26. Oktober 2023
Can I move discourse out of the default docker bridge network? Support	3	959	1. September 2021
Linking containers Self-hosting hosting	5	1511	31. März 2014

Benutzerdefinierte Docker-Netzwerkkonfiguration – Container-zu-Container-Kommunikation

Verwandte Themen