this post was submitted on 08 Oct 2023
22 points (95.8% liked)
Self Hosted - Self-hosting your services.
11406 readers
2 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@Tippon That is a big part of the point behind containers, you don't have any long term state inside them. Migration is just a case of copying the configuration over along with the contents of any persistent volumes.
It's worth looking into Podman instead of Docker, the daemon-less architecture makes it more lightweight and secure as it's easier to have rootless containers. Management can also be easer as being a Red Hat project it integrates well into Systemd.
With your existing server on Xubuntu you may as well stick with Ubuntu Server or Debian for the familiarity.
Podman also has tooling for deploying containers as systems services or as k8s deploymentments.
I have no idea what that means! (yet :D).
Time for some research :)
@andruid @Tippon Stay away from k8s for now, that's more for when you have a cluster of multiple physical servers. The systemd services are more useful in a single server environment.
The way that works is that once you have the containers set up, podman can save the configuration of them as unit files so they can be managed the same way as native server software. This makes it easier to have them all start automatically after a reboot, and is a requirement for enabling automatic updates.
Ah, ok. Thanks for the help :)
Brilliant :)
I've just been reading some of the other replies, and, yeah, it looks like containers are the way to go. I've got my data on separate drives, so that's easy enough to deal with, it's just the container side of things that's been confusing me.
I'll have a look at Podman, thanks :)
Like you say, I'm probably better off with a Debian fork, especially as I'm using Mint on my laptop, and should be on my PC if I can find alternatives to a few programs :)
I've been working with podman for a few weeks, and it's functional but a bit harder. If you're a noobie I would recommend you stick to docker. If you're a FOSS enthusiast and up for a little more challenge podman is pretty cool.