<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networks on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/networks/</link><description>Recent content in Networks on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 14 Aug 2017 18:56:00 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/networks/index.xml" rel="self" type="application/rss+xml"/><item><title>Security and convenience with Docker private networks</title><link>https://blog.sodawa.com/blog/security-and-convenience-with-docker-private-networks/</link><pubDate>Mon, 14 Aug 2017 18:56:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/security-and-convenience-with-docker-private-networks/</guid><description>Docker is great, and I do not want to write much about what it does, but rather a problem that I have faced in my setup.
What I wanted to do was hosting a webserver inside of 1 container and a git client (https://github.com/go-gitea/gitea) in another. The webserver should be able to proxy requests from a certain url to the git client.
First attempt What I did first was exposing a port on my git client as follows:</description></item></channel></rss>