Hello, I try to add a command to the app.yml file to add an entry to the host file in the docker container at the rebuild. But this command never works and i can’t understand why :zipper_mouth_face: run: - exec: "echo '192.168.0.1 custom.domain.fr' >> /etc/hosts" Any how to update the /etc/hosts at rebuild ?

[image] Chopper: Any how to update the /etc/hosts at rebuild ? Okay, I figured it out. You cannot use the yml file because /etc/hosts is created at runtime by Docker itself. To add entries to it, you need to use the --docker-args option to launcher at rebuild time. ./launcher rebuild app --docker-args "--add-host extra.dns:8.8.8.8" ./launcher enter app grep extra /etc/hosts 8.8.8.8 extra.dns There are a slew of dns / resolver / similar options for docker run, and those are the ones you need to use for this sort of stuff.

Pretty sure your quotes are wrong. run: - exec: echo '192.168.0.1 custom.domain.fr' >> /etc/hosts The issue seems to be, that command will work just fine, but will be lost on container start. Go ahead and enter the container, run the command by hand, then restart it: ./launcher enter app echo '192.168.0.1 custom.domain.fr' >> /etc/hosts grep custom /etc/hosts 192.168.0.1 custom.domain.fr exit ./launcher restart app ./launcher enter app grep custom /etc/hosts Not quite sure what process is rewriting the /etc/hosts file. This works: ./launcher start app docker exec -it app bash -c "echo 192.168.0.1 custom.domain.fr >> /etc/hosts" But you’d need to do that every start. (And if you try to modify launcher to do that for you, launcher will get upset when it can’t update itself with git. Ask me how I know this? I’ve done that.)

Hummm ! Intersting :+1: Meaning I cannot use /admin/upgrade to update to Discourse :zipper_mouth_face:

Well, here’s a slightly messy alternative. Changes to /etc/hosts file are effectively immediate for the system. Docker creates the file at boot time, while setting up all of the container internal networking. But after that Docker leaves it alone. A “plug-in” that inserted itself into late system boot could add values to the /etc/hosts file. (Or could be a script created via yml.) I might try to tackle that later today.

Even the update on docker_manager ? :face_with_raised_eyebrow:

Yep, updating docker_manager just updates the docker_manager discourse plugin, which contains all the scripts for updates. It still doesn’t even restart the container, let alone rebuild it.

Huh, add to list of things I didn’t realize. Never paid that much attention to what was happening, since it always just worked. :blush:

This bash script is checking if smtp entry is defined in /etc/hosts in docker container: file: check_hosts_entry #!/usr/bin/env bash smtp=$(docker exec -t app bash -c "cat /etc/hosts | grep -m 1 your_smtp_domain" | tr -d '\r'); if [[ "$smtp" != "your.ip your_smtp_domain" ]]; then echo 'No SMTP entry. Adding it...'; docker exec -t app bash -c "echo your.ip your_smtp_domain >> /etc/hosts"; else echo 'The SMTP entry is already there!'; fi crontab Add it to your host’s crontab to be run every 30 mins or whatever you like: */30 * * * * /root/bin/check_hosts_entry >/tmp/stdout.log 2>/tmp/stderr.log *Don’t forget to replace your.ip and your_smtp_domain with your specific data :wink:

Update /etc/hosts at rebuild

Product Support Self-hosting

david (David Taylor) August 25, 2017, 2:56pm 6

/admin/upgrade shouldn’t touch the /etc/hosts file - it just updates stuff within the docker container, it doesn’t do a full rebuild.

Topic		Replies	Views
Adding an entry in hosts file Self-hosting docker	2	1074	June 13, 2023
How do I rebuild app using the host network rather than the docker network? Self-hosting	10	2258	June 24, 2021
Changing the hostname Product Support docker	6	7027	November 12, 2018
Help after updating from ssh site goes down Self-hosting	6	1162	January 30, 2022
Could not resolve host: github.com for SamSaffron/pups.git Product Support docker	11	12120	November 12, 2020

Update /etc/hosts at rebuild

Related topics