From last week's Linux Update newsletter: Koen Vervloesem shows you how to manage containers with MicroOS, Cockpit, and Podman
https://www.linux-magazine.com/Issues/2025/291/Container-Management?utm_source=SM
#containers #openSUSE #MicroOS #Cockpit #Podman #Docker
If you're curious as to why now, why the rush when we committed to it, and why it's one of the first things I tackled:
- I had done some Patternfly v6 upgrade work in @packit already - not much compared to Cockpit but still enough to get accustomed to a lot of the components.
- Patternfly v5 had lots of bugs we worked around but the Patternfly team only supports v6.
- I want to get a better relationship between Cockpit and Patternfly to reduce the long-term technical debt and handle issues we encounter better.
- Lots of our workarounds are fixed, and more so in v6, so it is going to reduce our own codebase a fair amount over time (workarounds are still in our codebase with the upgrade to reduce PR complexity, but will be removed over time).
- Cockpit can now get better theming with Patternfly tokens - AKA CSS variables.
- Patternfly v6 has been out for a while and all the bigger issues are fixed. We did encounter a fair amount of bugs here and there which the Patternfly team is now aware of - one is getting a patch-fix soon relating to screen-reader accessibility!
#cockpit
Some stats and info:
- Proof of concept/spike work started when the PR started - Feb 12th.
- Viability of plugin migration spike in cockpit-files started on Feb 12th.
- Team decided we will soon have time to do the Patternfly v6 upgrade, continued my work more seriously on Feb 25th.
- Team-wide commitment to the upgrade happened on March 12th.
- We totaled around ~90 unique commits to change various aspects.
- I had done the brunt work, but all team members had a hand in the upgrade due to a bunch of smaller issues. Last week there was work to upgrade cockpit-files already started by Jelle and cockpit-machines saw some attention to the upgrade by Marius.
- For the team-wide effort in the one PR, our goal was that all tests pass and we have verified the pixel/visual tests and agreed on any regressions
- All the work in the PR was split by test case to reduce the overlap. Other code-wide issues were planned how to do in Matrix
#cockpit
Oh hey my first real feature got merged to Cockpit now (upgrading the UI library)
Now comes the fun part of follow-up PRs to improve various aspects of the design, as well as updating the Cockpit-owned plugins
github.com/cockpit-project/cockpit/pull/21611
#cockpit
I'm curious to hear what others are #SelfHosting! Here's my current setup:
Hardware & OS
Infrastructure & Networking
Security & Monitoring
Authentication & Identity Management
Productivity & Personal Tools
#CookingAppsNotifications & Development Workflow
Accessibility Focus 
️
Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!
I've also experimented with:
I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services! 
What's your setup like? Any cool services you'd recommend I try?
#SelfHosted #LinuxSelfHost #OpenSource #TechCommunity #FOSS #TechDIY
Wanted to set up old laptop as a #homelab VM server but didn't want the complexity of #proxmox for my basic needs. #Truenas scale might have been ok except for the need for a dedicated boot device. Dropped on Redhat's "#cockpit machines" today and so far it seems perfect, very easy to spin up new VMs and access them through a polished web UI, as well as manage the host itself. Feel like this project deserves better recognition #linux
This week's #cockpit release has become a lot SMARTer! 
(Don't worry, it's not AI).
Are you currently using #Cockpit with the builtin self-signed #TLS #certificate fallback? We would like to deprecate this, but need your input for that. Thank you in advance!
https://github.com/cockpit-project/cockpit/discussions/21695
Here is a screen recording of the most up-to-date progress on upgrading Cockpit to Patternfly v6!
It's a big change for sure but over a longer period of time it'll look better and better ~
Hopefully with Patternfly having their token system - themeing with CSS variables - I can even create a custom theme for "Gockpit" or something uwu
#cockpit
Mobile navigation for Cockpit upgrade to Patternfly v6 is now pretty complete. Slowly but steadily all the pieces for the migration are falling into place and will soon become a focus for the project itself to prioritize before a release.
Most changes we'll be doing as a team is sanity checking things, updating dependencies, checking pixel tests, and checking applications like cockpit-files are upgraded too.
#cockpit
@ryan as others have stated, Ansible is great. Jeff Geerling's Ansible book is now free and he has a lot of good content on his site.
https://leanpub.com/ansible-for-devops/c/CTVMPCbEeXd3
To get a good overview of the fleet, however, Cockpit is awesome.
https://cockpit-project.org/
@nigelharpur may i suggest #cockpit to access the server? I just ssh to mine and nvim/vim the mods for my #luanti / #minetest server
This week's #cockpit releases add Apple compatible keyboard shortcuts to cockpit Files.
With some of the Cockpit migration to Patternfly v6 I've gotten quite a bit of progress in scoping out various issues that needs addressing.
Kinda starting to look like something! Now to note down the issues I found in the PR
#cockpit
Good morning! 
A #MySoCalledSudoLife update: your replies yesterday convinced me to try one more time to install #Ghost with commands, thus bypassing “easy” solutions like PaaS (platforms as a service) that do the job for you (Coolify, CasaOS, Dokploy).
My main reason for this, really: I don’t want to rely on something that - if it is discontinued - holds all the power on my Ghost installation. So going the sudo way.
Now, I’ve been doing a bit of reasearch on alternatives to PaaS that make the Ubuntu experience more accessible to newbies and I stumbled upon #Cockpit, a web-based graphical interface for servers: https://cockpit-project.org/ I think it may be a nice compromise? Do you have any opinions about it?
I could wipe my Ubuntu VPS today (the one with the botched Ghost installation), try installing Ghost again with commands and then install Cockpit on the server too? I would love your advice about this. Thank you in advance.
I’m SUPER grateful for all your brilliant tips and words of encouragement and I promise I will give back… even if it takes years (for me to become more proficient in this), striving to help fellow newbies out. I never get discouraged because of you 
Wishing you all a lovely day (and keep me posted about Cockpit - yay or nay?)
I Love Free Software Day!
At the moment we want to thank:
@debian
@ansible
#netbird
#docker
#portainer
@ntfy
@Cockpit
#adguardhome
#searxng
@nlnetlabs for #unbound
@nextcloud
#vaultwarden
#wgeasy
#obtainium
We are currently working on a simpler solution for individuals to achieve more digital privacy in their homes.
Easy maintenance and more or less simple installation ;)
1/3
This week's #cockpit release 333 adds pasting files into differently owned directories (if you are superuser).
