hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9.4K
active users

#proxmox

24 posts23 participants1 post today

I wrote something for myself, and figured it might be useful for others: a small service that automatically discovers LXCs and VMs in a Proxmox cluster and acts as a DNS server pointing to the IP(s) for them. It's called, somewhat unimaginatively... proxmox-service-discovery:
github.com/andrew-d/proxmox-se

As a short example: if you have a Proxmox cluster running lxc1, lxc2, and vm3, and you run proxmox-service-discovery with the "--dns-zone=example.com" option, then it will run a DNS server that answers queries for lxc1.example.com with all the IP addresses for lxc1, and so on for lxc2 and vm3.

It's pretty basic but well-tested, and seems to work well for my use-case. Feedback appreciated, along with bug reports, PRs, and so on!

A DNS server that automatically discovers VMs and containers (LXCs) in your Proxmox cluster and makes them available via DNS - andrew-d/proxmox-service-discovery
GitHubGitHub - andrew-d/proxmox-service-discovery: A DNS server that automatically discovers VMs and containers (LXCs) in your Proxmox cluster and makes them available via DNSA DNS server that automatically discovers VMs and containers (LXCs) in your Proxmox cluster and makes them available via DNS - andrew-d/proxmox-service-discovery

Hallo und guten Abend zusammen!

Für unser Projekt #mapleHome haben wir uns kürzlich einen neuen #homeserver gegönnt und bereiten und den Umzug unseres #Smarthome und einiger Apps/Tools vor. Bislang läuft unser #HomeAssistant OS auf einem Raspberry Pi 4 - soweit so gut.
Was mich persönlich immer nicht ganz so glücklich macht ist, dass die erforderlichen Add-ons und Zusatzdienste eben zu 100% vom gleichen System abhängen. So ist ja z.B. zigbee2mqtt ebenfalls "offline", wenn ein Update mit Neustart durchgeführt wird ...

Meine Idee:
Ich möchte zusätzliche Server/Dienste wie #zigbee2mqtt, den #MQTT Broker, Datenbanken, ... ein eigene VMs/Container auslagern. Dazu läuft #proxmox auf dem Server, für Home Assistant wird es eine VM geben und eben auch eine VM für #Docker.

Habt ihr es auch so oder so ähnlich umgesetzt? Bin ich gedanklich auf dem Holzweg? Oder würdet ihr noch weiter gehen?

Danke schonmal und allen einen schönen Sonntagabend!

Finally got around to migrating my home server to #Proxmox, and chucking my docker containers in a VM while migrating to running everything in #Kubernetes.

...only to be reminded that the idiot who built my home server (me) only bothered getting 16GB of RAM. Doesn't really stop any of my plans, but feels a bit silly to have a Proxmox machine so limited by RAM.

My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉

Previously, it supports
#Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.

Now, to reduce reliance on Plex and lean towards a completely
#FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.

I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my
#Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.

🔗 https://github.com/irfanhakim-as/charts/pull/136

Changes

Updated chart to match current base template
Added support for modularity for all containers - pick and choose what you need/don't
Made improvements to various var assignments and cond...
GitHubflex: General update by irfanhakim-as · Pull Request #136 · irfanhakim-as/chartsBy irfanhakim-as
Continued thread

but thankfully there are parts of my #surfhosting tech stack which are fairly settled already:

OS: #LinuxMint; #Debian (with #LXQt if needed, or #BunsenLabs); #OpenWRT

Virtualization: #Proxmox

Hardware: refurb "1-liter" #1LPC business #miniPC from HP, Dell, Lenovo, with mid to high end CPU

Network: #GLiNet and #FriendlyElec #NanoPi routers / network-attached devices; #PiVPN

Phone: #VoipMS with dedicated SIP phone, plus softphone apps for limited use

Power: 90% of everything powered from compact #GaN USB-PD power supplies; 24/7 gear backed by ~15 year old consumer UPSes with drop-in LFP 12V batteries

Tiens, Boradcom/#vmware change sa tarification : facturation de 72 cœurs minimum par cluster. ça tombe bien, on avait déjà décidé de migrer cette année toute notre infra sous #proxmox. Nous allons bien sûr prendre du support pour participer à la vie du projet.

des connaisseurs en #proxmox et #ntp ici ?
mon serveur proxmox n'est pas à l'heure

root@pve:~# timedatectl
Local time: Sat 2025-04-05 00:07:08 CEST
Universal time: Fri 2025-04-04 22:07:08 UTC
RTC time: Fri 2025-04-04 22:07:08
Time zone: Europe/Paris (CEST, +0200)
System clock synchronized: no
NTP service: active
RTC in local TZ: no

et pourtant NTP service est bien "active", qu'est ce qui ne va pas ?

Intento a smussare gli angoli di questa istanza #MaStoMondo fino a renderla perfetta. Che poi perfetta è un parolone nel mondo del #selfhosting. Al momento gira su una LXC #proxmox sull'home server che mi aiuta a rimediare via backup i danni irreversibili causati risolvendo altri problemi..

Prossima task: risolvere problema immagini dei miei post rotte o blurrate.

E pensare che 3 backup fa c'ero riuscito.

Continued thread

Was mir aber schleierhaft ist/ erstellt man einen neuen MON mit #proxmox GUI, hat der keine Rechte. Ich musste aus einer alten Node den Schlüssel kopieren. Erst dann lief es.

Ein paar Nacharbeiten stehen noch an, aber im Großen und Ganzen.. ok.