#quadlet — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #quadlet, aggregated by home.social.
-
Holly fucking christ am I annoyed by free chatbots capabilites of fixing problems. #ChatGPT #Grok fail so hard solving seemingly easy problems like #podman #quadlet configuration or simple user profile problems under #windows11 with specific policies in place. Instead they keep asking questions over and over instead of providing clear cut answers...
-
Woo woo. I am now confident with the new wiki document rewrite and some quadlet file changes. Tested deployment on my local machine and VM, both official upstream and Glitch-Soc.
Mastodon Rootless Podman Quadlets
NEW: Simplified Version
#rootless #quadlets #quadlet #podman #mastodon #sysadmin #mastoadmin #mastodev #deployment
-
Woo woo. I am now confident with the new wiki document rewrite and some quadlet file changes. Tested deployment on my local machine and VM, both official upstream and Glitch-Soc.
Mastodon Rootless Podman Quadlets
NEW: Simplified Version
#rootless #quadlets #quadlet #podman #mastodon #sysadmin #mastoadmin #mastodev #deployment
-
New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman
The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.
The filesystem is the API between CI and host.
-
New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman
The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.
The filesystem is the API between CI and host.
-
@cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.
For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.
-
@cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.
For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.
-
New blog post: Ansible-Native Quadlets: Deploying a Mastodon Greeter Bot with containers.podman
Hand-written Quadlet files are great for one host. For a small fleet, I want them in Ansible: templated config, registry login, Podman secrets, systemd handlers, SELinux labels, and repeatable deployment.
The example: a tiny Mastodon welcome bot running as a Podman Quadlet-managed systemd service.
#Linux #Ansible #Podman #Quadlet #systemd #Mastodon #SelfHosting #RHEL
-
New blog post: Ansible-Native Quadlets: Deploying a Mastodon Greeter Bot with containers.podman
Hand-written Quadlet files are great for one host. For a small fleet, I want them in Ansible: templated config, registry login, Podman secrets, systemd handlers, SELinux labels, and repeatable deployment.
The example: a tiny Mastodon welcome bot running as a Podman Quadlet-managed systemd service.
#Linux #Ansible #Podman #Quadlet #systemd #Mastodon #SelfHosting #RHEL
-
I decided to dedicate my weekend to server maintenance and documentation.
Yesterday, I managed to install Immich using Quadlets, following the instructions on this very insightful repository, then I tried to migrate a Nextcloud installation from YunoHost to my new homelab. I started a #tmux session so that @sirodoht could kindly join to help me. We tinkered for two hours, but there was too much to do 🤯
Today, I spent the whole day writing documentation for these and many other things I learned/did in the past couple of months, since I am terrible at taking notes of the technical experiments I do.
I am exhausted, but also quite discouraged. The more I write, the more I feel there is to write. I really think I don’t have the time and the energy, but when it’s done it’s very fulfilling, and it’s very useful to have a lot of references in the future.
I will edit this post once what I wrote gets published on tommi.space.
#Immich #Podman #Quadlet #Quadlets #systemd #Linux #containers #tmux #documentation
-
I decided to dedicate my weekend to server maintenance and documentation.
Yesterday, I managed to install Immich using Quadlets, following the instructions on this very insightful repository, then I tried to migrate a Nextcloud installation from YunoHost to my new homelab. I started a #tmux session so that @sirodoht could kindly join to help me. We tinkered for two hours, but there was too much to do 🤯
Today, I spent the whole day writing documentation for these and many other things I learned/did in the past couple of months, since I am terrible at taking notes of the technical experiments I do.
I am exhausted, but also quite discouraged. The more I write, the more I feel there is to write. I really think I don’t have the time and the energy, but when it’s done it’s very fulfilling, and it’s very useful to have a lot of references in the future.
I will edit this post once what I wrote gets published on tommi.space.
#Immich #Podman #Quadlet #Quadlets #systemd #Linux #containers #tmux #documentation
-
Sengaja tulis ini pakai akun misskey biar gak kejedot limit karakter.
Mengapa saya menggunakan dan menginstruksikan lingkungan yang berada dalam kendali saya menggunakan #podman bukan #docker dalam menjalankan #container
Pertama, docker membutuhkan daemon (yang defaultnya berjalan sebagai root) sedangkan podman sifatnya daemonless. Disini ada single point-of-failure. Sehingga jika ada bug atau apa, docker akan lebih rentan bisa menganggu host. Selain itu hal ini mengharuskan user yang ingin menjalankan container harus tergabung dalam group docker. Berbeda dengan podman dimana container yang dijalankan akan menjadi child-process dari user yang menjalankan.
Ada update pada runtime docker? Kita harus me-restart daemon docker dan artinya akan me-restart semua container yang berjalan.
Docker (katanya) fokus pada masing-masing container dan mengandalkan tool docker-compose untuk membungkus beberapa container, sedangkan podman mengenal konsep pod secara native yang menyerupai konsep pada pengoperasian #kubernetes. Bahkan podman bisa membuat yaml kubernetes dari pod.
Podman hanya kalah popular. Mungkin ini disebabkan karena docker adalah pelopor yang sukses. Mungkin anda akan berpikir kan banyaknya container-container yang tersedia adalah untuk docker seperti yang tersaji di Docker Hub. Tapi tahukah anda? Container image podman dan docker adalah sama, mengikuti standar OCI (Open Container Initiative). Jadi anda dapat menjalankan semua container image yang tersedia di Docker Hub dan container registry lain seperti #ghcr atau #quay dengan menggunakan podman.
Integrasi container-container dengan sistem juga akan lebih sederhana (kalau anda sudah menyadarinya). Docker menggunakan mekanisme sendiri untuk start/stop/restart container. Sedangkan container pada podman bisa sangat terintegrasi dengan #systemd, apalagi sejak dikenalkannya #quadlet. Format file quadlet sangatlah identik dengan file unit servis systemd. Dengan penggunaan quadlet, anda dapat start/stop/restart dengan menggunakan systemctl nya systemd.
PS: Penjelasan tadi adalah jawaban formal. Sebenarnya mengapa saya menggunakan podman adalah karena saya pengguna setia environment #Fedora dan #RHEL ✌✌✌✌✌ -
You might have noticed that I have spend some time in my Quadlets Repo, taking care of some Grafana stuff.
Took me a bit to understand it but I’m quite happy with the result.
Check it out if you’d like to deploy your Grafana instance with a few extras in your homelab!
#git #codeberg #monitoring #grafana #prometheus #NodeExporter #podmanexporter #tailscale #tailscaleexporter #podman #quadlet #quadlets #rootless
-
You might have noticed that I have spend some time in my Quadlets Repo, taking care of some Grafana stuff.
Took me a bit to understand it but I’m quite happy with the result.
Check it out if you’d like to deploy your Grafana instance with a few extras in your homelab!
#git #codeberg #monitoring #grafana #prometheus #NodeExporter #podmanexporter #tailscale #tailscaleexporter #podman #quadlet #quadlets #rootless
-
Out of boredom, I thought why not give the Zammad Quadlets another try.
Originally, I planned to work on them next month but I just couldn’t resist.And would you look at that, adding two more variables to the nginx container fixed the problem.
Now the Quadlets are working like a charm, meaning I need a new project for next month.
The wiki will probably be finished by the end of this week.
Check them out and give them a try by cloning my codeberg repo!
https://codeberg.org/Spoljarevic/Zammad-Podman-Quadlets/src/branch/master
#podman #quadlets #quadlet #podmanquadlets #coding #troubleshooting #codeberg #dns #repo #zammad #ticket #tickets #ticketsystem
-
A reminder to always RTFM (read the friendly manual of course).
I spend about an hour trying to get a Quadlet work.
After that I decided to go into the Arch wiki and would you look at that, there was this one single command that was missing in order to validate the Quadlet…I felt so stupid but my first .container file is up in my Quadlet Repo on Codeberg and I made a slim documentation for it (also linked the Arch Wiki there).
Took way longer than needed but I hope you enjoy!
-
Dear #mastoadmins, I'd like to improve the current setup using #caddy and #podman #compose. Is anyone using #podman #quadlet with #systemd? Also I understand that having the connection between caddy reverse proxy and mastodon via sockets is very cool and I'd like to give this a try as well.
Systemd is now offering keeping podman quadlet containers up to date by itself. Maybe this one can be leveraged as well.
-
Dear #mastoadmins, I'd like to improve the current setup using #caddy and #podman #compose. Is anyone using #podman #quadlet with #systemd? Also I understand that having the connection between caddy reverse proxy and mastodon via sockets is very cool and I'd like to give this a try as well.
Systemd is now offering keeping podman quadlet containers up to date by itself. Maybe this one can be leveraged as well.
-
Podman 5.8 :podman: just dropped and it's quietly setting the stage for 6.0.
The highlights:
- Quadlet multi-file install (bundle your whole stack in one file, finally)
- Automatic BoltDB -> SQLite migration
- AppArmor support in Quadlet unit files
- podman exec --no-session for faster exec callsIf you're running Quadlet-based deployments, this one's worth your attention.
-
Podman 5.8 :podman: just dropped and it's quietly setting the stage for 6.0.
The highlights:
- Quadlet multi-file install (bundle your whole stack in one file, finally)
- Automatic BoltDB -> SQLite migration
- AppArmor support in Quadlet unit files
- podman exec --no-session for faster exec callsIf you're running Quadlet-based deployments, this one's worth your attention.
-
Major learning curve to use #fedora #coreos is how to create ignition file. #FCOS installation use that for installation configuration. There's no menu or wizard like other #linux distros.
Why? Because one of major goal of #FCOS is to enable easy mass deployment of similar configuration.
After you learn and solved that problem, remaining else is just systemd and #podman #quadlet (most #fcos deployment is to run containerized applications)
-
Major learning curve to use #fedora #coreos is how to create ignition file. #FCOS installation use that for installation configuration. There's no menu or wizard like other #linux distros.
Why? Because one of major goal of #FCOS is to enable easy mass deployment of similar configuration.
After you learn and solved that problem, remaining else is just systemd and #podman #quadlet (most #fcos deployment is to run containerized applications)
-
✅ #livekit Installation für #Matrix #Web-RTC in naitve rootless Pods via #Quadlet.
Ich muss zu meiner Schande gestehen, dass ich bei der Integration von #systemd massiv auf AI zurückgegriffen habe. Bin mir nicht sicher, ob ich das allein hin bekommen hätte.
Das muss einfacher werden!
Jetzt fehlt noch die Anbindung an den ReverseProxy, dann sollten A/V-Calls auch mit #ElementX klappen.
-
My #quadlet repository continues to turn more and more into a documentation project...
-
I’ve officially stopped using generate_systemd for my Podman deployments.
I updated my Ansible playbooks to use the Quadlet support in the containers.podman collection (state: quadlet).
Instead of scripting podman run commands or managing complex systemd unit files manually, Ansible now defines the container as a systemd service natively.
The result?
Rootless by default.
Auto-updates enabled (AutoUpdate=registry).
Zero drift.
If you’re running RHEL at the edge, this is the architecture you want.
:ansible: ❤️ :podman:
-
I’ve officially stopped using generate_systemd for my Podman deployments.
I updated my Ansible playbooks to use the Quadlet support in the containers.podman collection (state: quadlet).
Instead of scripting podman run commands or managing complex systemd unit files manually, Ansible now defines the container as a systemd service natively.
The result?
Rootless by default.
Auto-updates enabled (AutoUpdate=registry).
Zero drift.
If you’re running RHEL at the edge, this is the architecture you want.
:ansible: ❤️ :podman:
-
🚀 Upgrade de #Backup al meu servidor! 💾
Fins ara feia servir #Restic amb scripts shell per gestionar tots els meus #backups, i funcionava bé.
Però acabo d'instal·lar #Zerobyte com a #Quadlet al servidor... i és una autèntica passada! 🤯
És un front-end brutal per a #Restic per monitoritzar, restaurar i gestionar els repos sigui increïblement fàcil. Recomanat 100% si feu servir #Restic!
-
🚀 Upgrade de #Backup al meu servidor! 💾
Fins ara feia servir #Restic amb scripts shell per gestionar tots els meus #backups, i funcionava bé.
Però acabo d'instal·lar #Zerobyte com a #Quadlet al servidor... i és una autèntica passada! 🤯
És un front-end brutal per a #Restic per monitoritzar, restaurar i gestionar els repos sigui increïblement fàcil. Recomanat 100% si feu servir #Restic!
-
Bagaimana kami menjalankan instance #mastodon ini menjadikan sumber inspirasi buat kami untuk menjabarkan step-by-step menjalankan #container mastodon dengan #podman #quadlet
https://blog.kodesumber.com/posts/container-mastodon-dengan-menggunakan-quadlet-podman/
-
Bagaimana kami menjalankan instance #mastodon ini menjadikan sumber inspirasi buat kami untuk menjabarkan step-by-step menjalankan #container mastodon dengan #podman #quadlet
https://blog.kodesumber.com/posts/container-mastodon-dengan-menggunakan-quadlet-podman/
-
Question for #systemd #quadlet gurus: what do y'all do for running different services properly segregated that have persistent data needs? My first attempt was to add system users with user systemd instances (kind of like I would've done previously with just service users), and while that *works*, I definitely feel like I'm fighting systemd the whole way. Dynamic users are tempting, but I'm not grokking how data ownership would work when the UID presumably isn't stable across reboots. I'm sure I'm holding it wrong, but I'm not quite getting what the right way is
