SeeJayEmm

joined 2 years ago
[–] [email protected] 13 points 5 months ago

We don't? We lost. I'm going to go back to huddling in the corner.

[–] [email protected] 1 points 5 months ago

I run docker exclusively in VMs and VPS and it works fine.

[–] [email protected] 1 points 5 months ago
[–] [email protected] 4 points 6 months ago (2 children)

So Grocy doesn't directly support OIDC/SAML but it does support auth being passed along via the reverse proxy. This is how my grocy is configured. No double logins required.

[–] [email protected] 2 points 6 months ago (2 children)

I'm going to add Hoarder to the pile of suggestions.

[–] [email protected] 18 points 6 months ago (9 children)

A VPS is already a VM and nesting VMs, even if you get it to work, is generally a Bad Idea™️.

What you're asking for is squarely in "bare metal" territory. Does that reduce your flexibility? Sure. But it doesn't entirely eliminate it. Down the road if you decide you need more RAM or disk those are things you can have added (at a cost). CPU would likely necessitate a migration to a different system so I'd keep that in mind during initial sizing. Also, if you are using proxmox, migration will be as simple as backing up a container/VM and restoring it at the destination.

Your other alternative is multiple VPSes or possibly augmenting the bare metal server with one or more VPSes.

As far as unified billing goes, just have all the services with the same provider. Most providers I've encountered offer both services.

I can't speak to providers in our around Sydney, but I'd recommend checking out lowendbox.com to start your search.

[–] [email protected] 0 points 6 months ago

Only by exposing the docker socket. And it doesn't support managing network or volumes.

[–] [email protected] 8 points 6 months ago

The constant argument in this space that you must know the arcane workings of everything you use, is exhausting.

[–] [email protected] 1 points 6 months ago (3 children)

Just because something doesn't fit your use case doesn't make it a terrible product. Portainer isn't meant to complement managing docker via CLI. It's meant to be the management interface.

If you want to manage your environment via CLI, I agree, don't use Portainer. If you're content (or prefer) a GUI, Portainer is a solid option. Esp if you have multiple hosts or want to manage more than just the compose stack. Last time I checked Dockge doesn't do either.

[–] [email protected] 2 points 6 months ago

Personal preference? I prefer the Portainer's presentation over the CLI. I especially find it easier to manage networks and volumes.

But my main reason is I have multiple docker hosts and it gives me a "single pane on glass" to manage everything from.

[–] [email protected] 5 points 7 months ago (1 children)

soft meow

You've obviously never met my cat.

1
VM vs Docker container (lemmy.procrastinati.org)
 

Hi. I currently run plex in a kvm VM. Have for years without any real trouble. I'm in the process of refreshing my homelab and replacing the plex VM is next on my list.

I'm curious if there are any pros or cons to running Plex in a docker container vs it's own dedicated VM? Is there anyone here who's done both and saw a difference?

view more: next ›