@ -15,14 +15,14 @@ OpenVSwitch would allow me to add features like **Firewall as a Service** or **I
BUT these servers are all in production, i can't play on them, this is where [Mininet](http://mininet.org/ "Mininet") comes in use, it allows me to emulate a full network on a single VM, without touching these root Servers.
Have a look at this [Script](https://gist.github.com/pcdummy/9b9d1589289b649d8207 "hetzner.py") if you also need a lab to test your Hetzner Networking.
Have a look at this [Script](https://gist.github.com/jochumdev/9b9d1589289b649d8207 "hetzner.py") if you also need a lab to test your Hetzner Networking.
Setup from start:
1. At first get and install a [Mininet Download and Guide](http://mininet.org/download/ "Mininet Download and Guide") also see this [Guide](http://www.brianlinkletter.com/set-up-mininet/ "Mininet Setup guide by Brian Kletter")
2. Learn howto use Mininet [Sample Workflow.](http://mininet.org/sample-workflow/ "Mininet Sample Workflow")
3. Edit the Script parameters in "[root_network](https://gist.github.com/pcdummy/9b9d1589289b649d8207#file-hetzner-py-L257 "Script root_network")" (get the gw mac with `$ arp -n` on your root.
4. Next copy the [Script](https://gist.github.com/pcdummy/9b9d1589289b649d8207 "Script") to your VM: `$ scp hetzner.py mininet@<vm-ip>:/home/mininet/` (you might want to use sshfs).
3. Edit the Script parameters in "[root_network](https://gist.github.com/jochumdev/9b9d1589289b649d8207#file-hetzner-py-L257 "Script root_network")" (get the gw mac with `$ arp -n` on your root.
4. Next copy the [Script](https://gist.github.com/jochumdev/9b9d1589289b649d8207 "Script") to your VM: `$ scp hetzner.py mininet@<vm-ip>:/home/mininet/` (you might want to use sshfs).
Today i moved my wordpress blog to hugo, it will allow me to **post faster** use **less resources** and i can **share** my content **on [github](https://github.com/pcdummy/pc-dummy.net)**.
Today i moved my wordpress blog to hugo, it will allow me to **post faster** use **less resources** and i can **share** my content **on [github](https://github.com/jochumdev/pc-dummy.net)**.
I've been using Markdown a lot recently to document my own stuff,
now i'm able to just copy it to my blog and publish it.
An howto on systemd with a Debian stretch/buster docker container and Gitlab.
<!--more-->
Find all code on Github [stretch](https://github.com/pcdummy/proxmox-dockerfiles/tree/master/stretch-systemd) and [buster](https://github.com/pcdummy/proxmox-dockerfiles/tree/master/buster-systemd).
Find all code on Github [stretch](https://github.com/jochumdev/proxmox-dockerfiles/tree/master/stretch-systemd) and [buster](https://github.com/jochumdev/proxmox-dockerfiles/tree/master/buster-systemd).
### Debian Stretch
This didn't work at all with systemd from Debian stretch, but as i knew from my LXD experience systemd in stretch is buggy with containers,
so i tried systemd from [stretch-backports](https://github.com/pcdummy/proxmox-dockerfiles/blob/master/stretch-systemd/Dockerfile#L18) which worked well.
so i tried systemd from [stretch-backports](https://github.com/jochumdev/proxmox-dockerfiles/blob/master/stretch-systemd/Dockerfile#L18) which worked well.
Now to have systemd finaly working in a stretch container you need to mount a tmpfs into /run and /run/lock else systemd tries to mount those - fails with permission denied and freezes.