this post was submitted on 06 Nov 2023
35 points (94.9% liked)

Selfhosted

40173 readers
1047 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 1 year ago
MODERATORS
 

As the title states, how would you set it up? I've got an HP EliteDesk G5, what are the strengths and weaknesses of either:

  • ProxMox with one VM running TrueNAS and another VM running Nextcloud
  • TrueNAS on bare metal with Nextcloud running in docker
  • Some other setup

I'd like to be able to easily expand and backup the storage available to Nextcloud as needed and I'd also like the ability to add additional VMs/containers/services as needed

you are viewing a single comment's thread
view the rest of the comments
[–] PeachMan@lemmy.world 4 points 1 year ago (1 children)

Honestly I haven't used Proxmox, but I assume they can share storage without having to set it up like a network drive? If not, SMB would work.

[–] Dran_Arcana@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

Proxmox uses scsi for disk images, which are single access only

Smb would be quite a lot of overhead, and it doesn't natively support linux filesystem permissions. You'll also run into issues with any older programs that rely on file locks to operate. nfs would be a much more appropriate choice. That said, apparmor in container images will usually prevent you from mounting remote nfs shares without jumping through hoops (that are in your way for a reason). You'll be limited to doing that with virtual machines only, no openvz/containerd.

Fun fact, it was literally the problems of sharing media storage between multiple workflows that got me to stop using virtual machines in proxmox and start building custom docker containers instead.

[–] atzanteol@sh.itjust.works 6 points 1 year ago (1 children)

You can do the NFS mount in the VM and share it as a volume with the docker container.

[–] Dran_Arcana@lemmy.world 2 points 1 year ago

Apparmor will complain and block the nfs mount unless you disable apparmor for the container. Then in a lot of cases the container won't be able to stop itself properly. At least that was my experience.