Installing Podman on Proxmox is rather straight forward. The initial idea for how to do this came from a post on the Serve the Home (STH) blog: Create the Ultimate Virtualization and Container Setup (KVM, LXC, Docker) with Management GUIs. In that article STH uses Docker and provides a Portainer GUI. In this example the Portainer GUI is going to be omitted and use Podman instead of Docker. The daemonless part of Podman is the real selling point.
Installing Home Assistant on Proxmox is relatively straightforward thanks to a script by Whiskerz007 on GitHub. I will not detail the steps here as they are pretty well documented both in the README and on the Home Assitant message boards. This topic is about migrating the data from an existing Home Assistant installation into HassOS. The complication is that HassOS mostly has a read-only file system and for whatever reason SCP is not working correctly.
In another post I explained how to force a specific EDID on boot. It requires patching the initramfs to contain the EDID and then patching GRUB. On Fedora, this is slightly different. So I wanted to cover that here. Install Patched EDID Install the patched EDID (this example uses the pre-patched EDID attached here) and modify GRUB to use the new EDID. sudo mkdir -p /lib/firmware/edid cd /lib/firmware/edid sudo wget https://gist.
NOTE: This guide is adapted from the OpenZFS project Wiki on installing Ubuntu 18.04 Root on ZFS. In some of the steps there are very specific parameters that are specific to my build and my environment. This post is meant to document my configuration. Step 1: Prepare The Install Environment 1.1 Boot the Ubuntu Live CD. Select Try Ubuntu. Connect your system to the Internet as appropriate (e.g. join your WiFi network).
To provide a local, and most likely newer, version of CMake than the system packages provide you can easily build it from source and install it to the systemd file-hierarchy spec which is an extension of the xdg user-dirs spec. The effect of this is there can be a fully functional CMake on the current user’s path and it will only be available to the current user. This is achieved by installing CMake to $HOME/.