queeup

Just thought I'd put together some detail on deploying Tailscale using Docker and Portainer. These bits-and-pieces are available elsewhere, but not together, so hopefully this will save someone a bit of time if you'd like to add Tailscale to an existing Docker install:

Here's my annotated recommended docker-compose, to use with Portainer-Stacks. Note that I'm not using a pre-made Auth Key. I started that way, but realized it was very easy to simply check the Portainer log for the tailscaled container once the stack is running. In that log you'll see the standard Auth link that you can use to authorize the container. This way you don't need to create a key in advance, or create a reusable key that introduces a security risk:

version: '3.9'
services:
  tailscale:
    image: tailscale/tailscale
    container_name: tailscaled

Using VSCode Flatpak to launch DevContainers Using Podman with Support for Nvidia CUDA and VSCode's "Container Features" In SilverBlue.

Note: This Setup Works for Machine Learning and GPU Acceleration in Containers

Setup

Make Sure you have rebased to UBlue-Nvidia.

Install Visual Studio Code

Enable Fractional Scaling Support on Wayland for Electron Applications

VSCode

vim .local/share/applications/code.desktop

[Desktop Entry]
Name=Visual Studio Code

How to make a new rpm-ostree desktop variant in Fedora?

So you want to make a new rpm-ostree desktop variant in Fedora to join Silverblue, Kinoite and Sericea? Here are the steps that you should follow.

First, you should figure out what packages should be installed in your image. To do that, you can start from the base container image (https://quay.io/repository/fedora-ostree-desktops/base) and add packages from the comps group corresponding to your desktop in Fedora : https://pagure.io/fedora-comps

At this point, you should consider which apps are going to be shipped by default, included in the image, and which ones are going to be installed by default as Flatpaks.

Once you've got something working, reproduce that in https://pagure.io/workstation-ostree-config using the comps group and the filter and sync script. Look at other variants for example.

ProxMox - Enable IOMMU using systemd

You found that you are using systemd, adding bits to GRUB will not work. Instead, follow these steps:

Edit the kernel command line

Open the /etc/kernel/cmdline file for editing:

nano /etc/kernel/cmdline

Fedora IOT AArch64 Kernel 6.2 Boot Fix

As reported by Fedora CoreOS team, on the AArch64 / ARM64 architecture the new 6.2 kernels will not boot due to older bootloaders in Fedora IoT.

Update

There is now some guidance from the Fedora IoT team on this here. This is probably the better course of action to take than my method below.

Usefull Android Apps

Opensource

Cloudstream

https://github.com/recloudstream/cloudstream/

Free netflix alternative.

Iceraven

Go to OpenWRT release page, select the latest release stable release, then targets -> x86 -> 64. Right-click generic-ext4-combined.img.gz (not the "efi"!) and copy the link.
On the Proxmox host, download the archive and unpack it:

wget *paste link here*
gunzip openwrt-*.img.gz

Resize the image to be the size you want your VM's disk to be (example with 8 GiB):

	version: "3.9"

	volumes:
	postgres:

	services:
	postgres:
	image: postgres
	restart: unless-stopped
	healthcheck:

	# WARNING: This is not how you should use a CI/CD plaftform, use privately and at your own risk
	name: URL uploader
	on:
	workflow_dispatch:
	inputs:
	LINK:
	type: string
	required: true
	FILENAME:
	type: string