this post was submitted on 30 Aug 2023
13 points (84.2% liked)

Selfhosted

40438 readers
460 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
13
Help me choose my setup, please! (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
17 comments fedilink hide all child comments
 

I have a server configuration to what i though would be best, and that is running a Debian, then installing a service i most frequently use, and use containers for other services. But, now i think that’s not a good solution and i’m looking for advice.

I thought of something like this:

Proxmox install Spin up a VM for this service that is currently running on Debian (can’t be in a container) Spin up a second VM, install Debian and Docker and install all other services as containers.

That would enable me to: a) backup the 1st VM to be able to deploy it if needed (backups) b) backup containers in the second VM so i can have them ready to be restored if needed

However, i’m not sure about setting it up like this. I’m worried if Jellyfin will work good as a container on a VM. Also, i’m worried about setting up nginx in a container on a VM, like, will it work as if installed on bare metal.

Other services i’m planning to run in containers on that 2nd VM are BookStack, Joplin, Mosquitto broker, Grafana, MariaDB, Influx DB, Studio Code, JellyFin, NectCloud etc.

The machine is a i3 1315U, 16GB RAM, 500GB SSD.

For the first VM i would allocate 2 cores and 4GB of RAM (that’s enough for what it does) and for the second VM (with all the containers) i would allocate the rest of the CPU and RAM.

Any advice is very welcome! Is proxmox still the best choice? Are there any other (better) choices? Is something obviously wrong with this setup?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 1 year ago (3 children)

To setup proxmox, you could install it on top of your current debian install : https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye

Docker in a lxc container is also used quite a lot with proxmox and would allow you to keep some resources without allocating everything for a docker VM.

[–] [email protected] 3 points 1 year ago (2 children)
[–] [email protected] 3 points 1 year ago (1 children)

I do exactly that, enable nesting in the lxc container, install docker and go from there. It works great

[–] [email protected] 1 points 1 year ago

Alright, i’ll check it out, thanks!