<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/docker/</link><description>Recent content in Docker on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 24 Jul 2019 07:40:03 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>debian, docker and nftables</title><link>https://blog.sodawa.com/blog/nftables-and-docker/</link><pubDate>Wed, 24 Jul 2019 07:40:03 +0000</pubDate><guid>https://blog.sodawa.com/blog/nftables-and-docker/</guid><description>Debian Buster ships with nf_tables as the firewall backend. So when installing it on one of my machines, I wanted to use the associated nftables frontend with it as well, instead of relying on the iptables-nft compatibility layer as a default.
After all, when would be a better time for learning it than now?
On the other hand I use docker quite extensively for my development environments, and docker uses iptables to set up the correct packet forwarding rules between containers and the host.</description></item><item><title>Gotede - quickly create a ghost theme development environment</title><link>https://blog.sodawa.com/blog/gotede-quickly-create-a-ghost-theme-development-environment/</link><pubDate>Tue, 11 Sep 2018 15:30:25 +0000</pubDate><guid>https://blog.sodawa.com/blog/gotede-quickly-create-a-ghost-theme-development-environment/</guid><description>When setting up a new theme for this blog, I ran into the issue of quickly setting up a development environment on my local machine to test out ideas.
So I went on to duckduckgo.com and quickly found this blog article.
Taking it as an inspiration I wrote a small script to publish on npm to make it easier for future themes and other people as well. You can find it at https://github.</description></item><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>