A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Portainer is just a docker container that manages other Docker containers. IMO, it's going down the enshittification hole. They chose to use a non-standard implementation of compose files, so you're stuck using Portainer unless you reconfigure your whole setup.
Proxmox, by contrast, is a hypervisor meant to run VMs and LXCs. The Proxmox devs have explicitly stated that nothing else should be running outside of it.
Could you tell me more about the non standard implementation? Coz I just use composerize to convert docker run commands to compose (or if I find compose files then hooray!) and pop those into portainer. Seems to work fine. I don’t like that a lot of features seem to be hidden behind a costly subscription, but thems the brakes.
As for proxmox… is it lighter weight than Debian?
Could you tell me more about the non standard implementation? Coz I just use composerize to convert docker run commands to compose (or if I find compose files then hooray!) and pop those into portainer. Seems to work fine.
Portainer is generally fine, but if you decide to migrate away from it, you will basically need to rebuild your whole compose stack setup.
I don’t like that a lot of features seem to be hidden behind a costly subscription, but thems the brakes.
Yeah, that was a big reason I moved away from it myself. They used to be way more flexible, but started really clamping down on free users a few years ago.
As for proxmox… is it lighter weight than Debian?
Proxmox uses Debian as its base OS, and since Proxmox is built to run full VMs, it isn't really comparable to running Docker containers on bare metal. You can run multiple Docker stacks inside a VM (including Portainer) - I do this with several VMs. But running a full VM inside a hypervisor on top of already-stressed hardware is probably a tall ask. So in your case, I would stick to Debian with Docker on bare metal.
The other thing I'm curious about - are you running a desktop environment on this machine? Or is it running headless? A DE will take up a lot of resources that the N5095 is already short on, and that CPU isn't exactly a great contender for streaming, either... It tends to fall on it's face if running much more than a single stream - including other services.
Proxmox is based on debian and uses debian under the hood...
Oh that’s awesome to know!!
@damnthefilibuster Is it a subjective impression or do you have information about used ressources on your device?
Are you running something like Beszel for getting information about the used ressources, especial from running containers?
https://github.com/henrygd/beszel
I'm running my services with rootless podman, but I can't compare it with docker. It's more related to security reason.
Thanks for that link! I'll run that service, collect some data and get back to you. I think it hits CPU limits though...
@damnthefilibuster There was just a post in my timeline about some applications for Docker Container Monitoring.
Maybe there are other alternatives, which fits better your needs:
Is it your cpu or your ram that hits the roof? Is it the host OS/Portainer or the services you run on it?
Here's how to check container usage in Portainer: https://docs.portainer.io/user/docker/containers/stats
The server kinda stops completely responding when it's doing a heavy download... so I can't get to those stats. But the other commenter has recommended I use https://github.com/henrygd/beszel so I'll check it out and see what the data reveals. I believe, based on how the system freezes up, that it must be the CPU hitting the roof.
I hope you find out that it's a not very necessary service that is the culprit, so that you can simply skip it. :)
I hope so too! It would be an unnecessary change.
If it's fanless, is it thermal throttling?
It’s fanless! How can I check for thermal throttling? Is that a bios setting?