Discuss
So I recently set up a VPS with YunoHost, it sounded neat. And for the most part it’s really nice having something take care of or simplifying most things regarding self hosting. Now the other day I decided to set up something via Docker (Sharkey, though that doesn’t really matter here I don’t think), and it mostly works. Some things within the containers need to communicate with other things in it, and it uses the domain name for it. Which resolves to 127.0.0.1:443, which, of course, doesn’t work. It has been driving me up the walls trying to figure this out and in the end I solved it by partially opening up one of the Docker containers (network type “host”) and just.. Killing dnsmasq.
The YunoHost admin panel didn’t like that, can’t check for updates anymore. Everything else seems to work fine without it. Now, I’ll admit I don’t know enough about networking/DNS to even start to figure out a nicer solution for this, but maybe someone here can? And if not, is there a way to tell YunoHost to just not use dnsmasq at all? Some other solution I haven’t thought of?