less than 1 minute read

This is not a good weekend. For me atleast…

  • Yesterday, an upgrade at work took longer than expected. Hence, had to call of external testing parties. Today I had to call them again, but most were not available. Joy for tomorrow.
  • Yesterday, windows decided to eat a partition which was on a Dynamic Disk. Scanned it today with GetDataBack, but only got half of my stuff back. No joy.
  • For some reason, parts of my linux installation broke themselves. No joy.
  • This morning, yet another thing broke at work, for obscure reasons. Even less joy.

Can this weekend be over and done already?

Updated:

Leave a comment

You may also enjoy

Using IPv6 outside of Docker with Docker

1 minute read

I recently activated IPv6 on my Netcup VPS, and in the process of setting it up on all my LXCs I noticed that for “reasons” the IPv6 default route would vanish after starting Docker (switching it all over to Podman is on my TODO list), effectively breaking the IPv6 connectivity on this LXC.

Enabling native IPv6 on Proxmox and LXC using SDN

3 minute read

In my original deployment of Proxmox on my VPS I only enabled IPv4, and I was using socat to forward traffic from the IPv6 address of the host to the internal IPv4 addresses of the containers. Not ideal, since this masks the external IP addresses, and also creates some latency and additional CPU load when processing IPv6.

Proxmox, LXC, and Debian Trixie

3 minute read

I run Proxmox Virtual Environment as my virtualisation platform. On top of this I use virtual machines using KVM and Linux Containers using LXC - both of which are natively supported on ProxmoxVE.

Code storage

1 minute read

Code, and where to store it