Selfhosted

59923 readers

511 users here now

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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Best way to manage all my services as containers? (lemmy.ca)

submitted 1 month ago* (last edited 1 month ago) by valar@lemmy.ca to c/selfhosted@lemmy.world

62 comments fedilink hide all child comments

What to people use and recommend for this? I've read a bit about portainer, but I'm still learning - and don't know what the best solutions are.

Today I have a handful of selfhosted services running on my home machine - mostly installed directly, but a couple running as docker containers. As the scale of my selfhosting has grown, I've realized that things would be a lot easier to manage if each service was run as its own container, so that installed services are isolated.

The solution I'm looking for would make it easy (possibly a web UI) for me to monitor, modify, update, and remove containerized services, including networking and storage.

Edit: Also I would only want a FOSS solution.

you are viewing a single comment's thread
view the rest of the comments

[–] K3can@lemmy.radio 2 points 2 weeks ago (1 children)

Podman quadlets can also auto-update and auto rollback, if needed.

[–] Andres4NY@social.ridetrans.it 0 points 2 weeks ago (1 children)

@K3can @silver How do you handle running as other users? I like to run services as their own user, so currently I create a new user and (as them) run podman compose.

[–] K3can@lemmy.radio 1 points 2 weeks ago (1 children)

Quadlets work like any other systemd service.

You create the user/group you want to run as on the underlying system, then just specify that user/group in the quadlet file.

If you look at my *arr examples, you can see the user and groups they're running as.

[–] Andres4NY@social.ridetrans.it 0 points 2 weeks ago (1 children)

@K3can So you're running the systemd services as root, and letting systemd change them to their relevant users? Or are you running the systemd services as a non-privileged user, and using container subuid/subgids?

[–] K3can@lemmy.radio 0 points 2 weeks ago

The first one. The service is owned by root, but the application is running as an unprivileged system user.