𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶

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

Yes there is.

https://github.com/grocy/grocy/issues/828

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.

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

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.

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

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

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.

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.

Yes to all of that.

Turns out it was a content update that caused the driver to crash but the update itself wasn’t a driver (as per their latest update.)

Is feel a lot better about this if it was a “supporter” tag not this “unlicensed” crap.

The hole is stripped not the screw head. The toothpicks give the screw something to grip.

I was really hoping this was going to be a rant about clouds in the sky.

Enough people have already commented on the “proxy at the vps solution”. Another option is to configure routing and nat on the VPS and have it route over the wg tunnel.

Requires you to have postup/predown scripts that modify your routing tables on the wg endpoint.

https://www.wireguard.com/protocol/

Looks like wireguard encrypts traffic to me.

Even with an outlet who wants to slow charge a plug-in EV? The infrastructure isn’t there and the cars are too expensive.

Using prions would be really harsh.