⑨ SSV @SplitShockVirus@distrotoot.com

Three days of this shit, think I might ask for a raise soon, shits getting old.

*ping*
>IPSEC Traffic Issue - EBTABLES Check
*ping*
>compute host disk low, migrate VMs
*ping*
>add ip range to these 3 VMs
*ping*
>Please attach recovery iso to this VM
*ping*
>connectivity lost for 3 VMs in this VLAN, please investigate
*ping*
>Please remove recovery iso from this VM
*ping*
>File level restore, failure please investigate
*ping*
>Add Secondary Drives to <client>
*ping*
>PRTG Disk Free: /var/lib/libvirt/images : <2TB
*ping*
>disk space for flattening disk image via blockpull

I hate the Anti-Christ
I hate Netplan
and I hate ebtables

I think I might setup Prometheus and Grafana to monitor my servers and services next.

I now have my own internal gitlab server 😎☕

TFW you install anything in a BSD jail

pic related

@numi #numi /id

gang

>be me
>get drunk last night
>update fedora with truecommand container because why not
>it should "just work™"
>docker fails to launch because of a "permission" error
>it doesn't "just work™"
>:^( I bet you it's fedora or that NSA bullshit
>go to bed
>wake up sober next day
>log into cockpit
>SELinux blocked 14 instances of docker containers

Yup it was the NSA

Yeah no nevermind, docker is a piece of shit and so is fedora (probably). The update introduced some sort of permission issue that didn't exist on 33 with launching containers (SELinux? NSA inside?).

I won't won't rollback this VM yet, and I'll troubleshoot this later, but needless to say I'm very disappointed with this development.

I updated Fedora to 34, now my docker container for truecommand won't start.

First time upgrading a Fedora machine. 33 to 34.

I have figured out how to pass kernel parameters into grub