Adam Kaminski thimslugga

Why Virtualize

you get full backups, snapshots, a build in monitor to debug. You can also better utilize the hardware. Not every service (very few imho) are feasible to run inside HAOS

easy troubleshooting (basically a build in monitor and keyboard), snapshots to test and then potentially revert things you otherwise would be too afraid to try. The ability to backup a whole machine and run other VMs/Containers and so on

I recommend running critical/unrelated things (adguard, unifi or bitwarden for example) or those that require flexibility outside of HAOS if you can as these will go down on OS updates. You can't do that with a bare metal HAOS install.

Some of my previous answers to why run HAOS virtualized. Just some of the benefits and reasons why I recommend it.

Podman quadlet example

quadlet-exec.sh - exec macro for quadlet containers

UPDATE: This is tested and working on both Linux and Windows 11 used for LlaMa & DeepSeek

Here's a sample README.md file written by Llama3.2 using this docker-compose.yaml file that explains the purpose and usage of the Docker Compose configuration:

ollama-portal

A multi-container Docker application for serving OLLAMA API.

VSCode + Dev Containers and Toolbx/Distrobox setup for Fedora Silverblue

PLEASE NOTE:

I personally don't use Flatpak VSCode anymore, since I switched from Fedora Silverblue to Universal Blue's project Bluefin-DX. I'll leave the instructions here for those who want them, but be aware that Flatpak VSCode instructions won't be maintained anymore.

Steps

If you prefer VSCode Flatpak

Install VSCode Flatpak from Flathub:

	{
	"HTML document": {
	"prefix": "html",
	"body": ["<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n\t<meta charset=\"UTF-8\">\n\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t<title>Document</title>\n</head>\n<body>\n$1\n</body>\n</html>", "$0"],
	"description": "HTML document"
	}
	}

	[project]
	name = "tool_testing"
	version = "0.1.0"
	description = "Ruff Tested Project"
	authors = [{ name = "", email = "" }]
	dependencies = []
	requires-python = "==3.11.*"
	readme = "README.md"
	license = { text = "MIT" }

	;===================== date: 20240606 =====================
	G92 E0
	G17
	G2 Z{layer_z + 0.4} I0.86 J0.86 P1 F20000 ; spiral lift a little
	G1 Z{max_layer_z + 0.4}
	{if !spiral_mode && print_sequence != "by object"}
	; don't support timelapse gcode in spiral_mode and by object sequence for I3 structure printer
	M622.1 S1 ; for prev firware, default turned on
	M1002 judge_flag timelapse_record_flag
	M622 J1

	/* Make sure to add following extensions:
	****************************************
	* 1. APC Customization UI++
	* 2. Symbols Icon Theme
	* 3. AbelFubu theme -> AbelFubu Contrast variant *Note: theme is only for syntax highlighting, ui colors are included in this file.
	* 4. Make sure to change a few settings like font, font size to your liking.
	****************************************
	*/

	{

	// Zed settings
	//
	// For information on how to configure Zed, see the Zed
	// documentation: https://zed.dev/docs/configuring-zed
	// Other guide: https://www.kevnu.com/en/posts/10
	//
	// To see all of Zed's default settings without changing your
	// custom settings, run the `open default settings` command
	// from the command palette or from `Zed` application menu.
	{

	substitutions:
	name: emporia-vue-v3
	friendly_name: Emporia Vue V3
	area: "Garage"

	# Circuit Labels used for publishing to Home Assistant
	circuit_1: "Dryer" #"Circuit 1"
	circuit_2: "AC Blower/Heat" #"Circuit 2"
	circuit_3: "AC Condenser" #"Circuit 3"
	circuit_4: "Water Heater" #"Circuit 4"