15 posts in Virtualisation
Started looking into a service to auto-post from this blog onto my Mastodon feed. Feed2Toot fit the bill perfectly.
I wanted to run the whole thing from a Docker container, though, so I'll quickly write a how-to.
This whole thing runs from a Raspberry Pi, as root. No k8s or k3s for me. The path I use is /root/git/feed2toot/, so be sure to modify that to whatever you're using.
I've revamped my Smokeping infra a bit since 2020.
First off, starting to use the smokeping.eu1 domain that Bianco got 10 or so years ago instead of using weird URLs under superuser.one domain.
It's running on four nodes as we speak:
This is achieved using Smokeping in a docker container, Cloudflare tunnel and Cloudflare CDN/DNS.
A couple of months ago I had the great idea to set up a shell server in Docker. Simply because my docker skillz were quite rusty and a shell server was something I actually genuinely needed.
Shell servers... so 2005. I remember in the good old IRC days people asking for (free) shell servers to run their eggdrop and stuff. OMG am I getting old? Anyhow...
I had the same theme for over four years. I’ve made quite a few custom css and PHP edits myself, and it had been outdated for ages… But it served me well.
However, it’s now time for something new.
As always, as minimalistic as possible.
On a side note, this blog has been moved from vm1 (and one before that) a virtual machine running on a dual Xeon 3070 (2.66Ghz) at Databarn to Akama, a VM on an 8 core Xeon E3-1230 (3.2Ghz) at Leaseweb.
Here’s my very simple Ansible playbook for Flightradar24 nodes.
While I run it on EfikaMX, it should work on most Debian based devices. Just be sure to modify the FR24 software download URL.
This Ansible playbook is untested on its own. It comes out of a way bigger (private) Ansible playbook, and I kind of just copy pasted this part, as others might benefit from it.
After running Ansible, you should reboot for driver blacklisting to work in cases it’s needed on your device (it is on RPis). And be sure to edit /root/flightradar24.sh with your key.
Note to self: <1Gb of RAM on a Dom0 Wheezy server causes kernel panics.
Using 2Gb of RAM seems to do the trick.
If you have a rc.local looking like this:
/bin/run-parts /etc/rc.local.d
and files in /etc/rc.local.d looking like this
hostname.sh sshkeys.sh firstboot.sh
it’s not going to work.
Why, you ask, after cursing and shouting for the past hour?
because run-parts ignores files with dots (".") and/or .sh files.
Yes. True story.
rename all the files to:
hostname sshkeys firstboot
and your problem will be solved (and of course chmod +x them).
In /etc/fstab, be sure to add the option:
_netdev
As it will attempt to start the network mounted sshfs before networking has been started.
The entire line looks like this:
user@host:/some/dir /local/path fuse.sshfs defaults,idmap=user,_netdev 0 0
From the man pages:
_netdev
The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).
Yay, after some hardware issues my blog’s back.
Zero had a corrupt reiserfs. Decommissioned the old P4 and replaced by a brand new dual Xeon. Running Xen and Debian instead of Gentoo.
And shortly there after Four (the server that hosts this VM), the Ubuntu host with Xen refused to start its networking, so I decided to start a fresh install (Debian as well this time).
One, who also had a broken hard disk (an old P3) got decommed as well.
