Hello everyone,
My home server (intel nuc6) died on me recently, I set it to be used as my home server using OpensSUSE Leap with the following services:
NFS server
Sftp over ssh for remote file transfers and I was looking for a faster alternative for local transfers (tftp maybe)
Qbittorrent
Aria2
Emby
I was experiencing with nextcloud then pfsense after.
Definitely an office suite and a few nextcloud addons.
I have no alternative machine ATM to use it as a replacement but I plan to re-install everything on a VM (Virtualbox or Qemu/libvirt) on my Desktop, I have no experience with containers, but I think installing each service in a countainer would make it easier to move everything later to my new home server.
Would using debian or opensuse and use docker? Maybe even proxmox? or should I just stick with installing everything directly on my distro with no containers?
I would love to know your opinion about the best approach.
Edit:
I’m containerizing, I like to keep my setup simple, no OSes vertualization since I will be using a 7th or 8th gen low power minipc for my next server (Intel NUC, Hp mini, dell micro or lenovo tiny). I will use proxmox in the VM to get confortable with it and I think the web UI might be easier to use than SSHing to the VM. Later on the new server I will mostly use debain+docker (opensuse leap’s futur is cloudy atm)
I would still love your suggestions and any guide/tutorial that you think is helpful to read/watch.
Thanks everyone.
From a user point of view, podman is mostly identical to docker. Like 98% of the time you can just replace ‘docker’ with ‘podman’ and it works. How they work under the hood is very different, though. Podman is designed around running rootless and daemonless. But if you don’t care about those things, use docker. Docker supports rootless as well now anyway, but you need to set it up manually. The biggest difference I have found is that podman doesn’t support docker-compose, which is extremely popular. Lemmy uses it, for example. There’s an additional couple of packages you can install that add support for docker-compose, but then podman uses a daemon, which defeats one of the purposes of using podman in the first place.
My workaround that I use for btrfs and systemd files is to have a folder in /etc with all my service files, then I soft link them to my service’s directory. This is just for organization purposes, as a backup wouldn’t include the data of the systemd file, just the link to it.
Thanks foe explaining, I know podman is rootless. My service where running their own non-login users (qbituser for qbitorrent, emby for emby and so own) and I needed to sudo if I want to change anything. It’s not a big deal for me so Docker seems easier to use.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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 posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
From a user point of view, podman is mostly identical to docker. Like 98% of the time you can just replace ‘docker’ with ‘podman’ and it works. How they work under the hood is very different, though. Podman is designed around running rootless and daemonless. But if you don’t care about those things, use docker. Docker supports rootless as well now anyway, but you need to set it up manually. The biggest difference I have found is that podman doesn’t support docker-compose, which is extremely popular. Lemmy uses it, for example. There’s an additional couple of packages you can install that add support for docker-compose, but then podman uses a daemon, which defeats one of the purposes of using podman in the first place.
My workaround that I use for btrfs and systemd files is to have a folder in /etc with all my service files, then I soft link them to my service’s directory. This is just for organization purposes, as a backup wouldn’t include the data of the systemd file, just the link to it.
Thanks foe explaining, I know podman is rootless. My service where running their own non-login users (qbituser for qbitorrent, emby for emby and so own) and I needed to sudo if I want to change anything. It’s not a big deal for me so Docker seems easier to use.