<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>external-ip on Purinda Gunasekara</title>
		<link>https://purinda.com/tags/external-ip/</link>
		<description>Recent content in external-ip on Purinda Gunasekara</description>
		<generator>Hugo</generator>
		<language>en-AU</language>
		
		
		
		
			<lastBuildDate>Sun, 17 Apr 2022 21:22:04 +1000</lastBuildDate>
		
			<atom:link href="https://purinda.com/tags/external-ip/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Docker – External IP for Your Docker App</title>
				<link>https://purinda.com/posts/docker-external-ip-for-your-docker-app/</link>
				<pubDate>Sun, 17 Apr 2022 21:22:04 +1000</pubDate>
				<guid>https://purinda.com/posts/docker-external-ip-for-your-docker-app/</guid>
				<description>&lt;h2 id=&#34;back-story&#34;&gt;Back story &lt;a class=&#34;anchor&#34; href=&#34;#back-story&#34; aria-label=&#34;Link to this section&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;I was playing around with Pi-hole on my Ubuntu host and got stuck when I was starting up the container with 53, 67 (udp / tcp both) was getting errors (“listen udp4 0.0.0.0:53: bind: address already in use”) because the Ubuntu host system itself were using those ports.&lt;/p&gt;&#xA;&lt;p&gt;I have previously used reverse-proxies to get around such problems but this time I wanted a simpler solution so I don’t have to manage another service in my local network to run Pi-hole.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
