docker-volume-backup VS docker-minecraft-server

I am interested in coming up with a backup plan before I get too invested in this setup. I found the docker-volume-backup project that looks like it might be a possible solution. However I'm not sure how to implement it using docker swarm since I am new to all of this. I would be interested in learning what backup solution you use for your docker swarm servers.

How do people usually backup their self-hosted docker services using postgres? I have been using docker-volume-backup [0] and just saving the postgres data directory, but I've found it requires a minute of downtime to backup properly.

[0] https://github.com/offen/docker-volume-backup

Offen: https://github.com/offen/docker-volume-backup

To solve points 1,2 i 3 I think it would be best to make the copy by stopping the container first. I've been looking for utilities and I've found some like offen/docker-volume-backup. Again, the disadvantage is that you have to configure everything (mount points, files, users, passwords...) manually for each container, so it is very easy to forget to create the backup of one of them. Also, the scheduling would not be centralised, so the backup wouldn't be run sequentially container after container. I've searched a lot, but I haven't found any good alternative. How are you dealing with the backup of containers?

Since I'm using docker rootless, I've run into issues using convenient solutions such as offen. These solutions don't work in a rootless context due to file permissions. The user in the offen container cannot read some directories owned by other containers. This is usually an issue with databases.

FYI this looks like the actively developed version of that utility: https://github.com/offen/docker-volume-backup

You should have backup OS and data but using a separate backup jobs. Backup OS drive using Timeshift or Veeam Agent. Backup Docker server's containers using Offen or Borg. OS backup would allow you restore operating system while data backup would allow recover files.

There is the image docker-volume-backup that allows you to make backup but depending on the situation (databases, ...) it is not necessarily the best solution

Looks nice! I have a comprehensive docker compose file with itzg’s image [0] repeated a dozen times.

[0] https://github.com/itzg/docker-minecraft-server

This is just from a quick search: https://github.com/itzg/docker-minecraft-server

I'd like something like this that works with the itzg docker image. I usually have 2-3 servers up and running at any given time for me and my kids to play on. Different modpacks, haven't done anything fancy to manage them except portainer.

I have a nephew who loves minecraft (my fault, I introduced it to him). He plays it on PS4 - which I don't have - and he would like to play it together with me. I live a few thousand kilometers away, so I thought I'd host a server he can join to.I decided to host the server via docker, using itgz's repo. The server is unauthenticated and is exposed to the internet, I can join to it using my java instance.

I think that a better option would be to use https://github.com/itzg/docker-minecraft-server and then use a networking solution like tailscale or equivalent.

using itzg/docker-minecraft-server to host a curseforge modded server that's running all the mods 8 mod pack, though I might look into pterodactyl for future use!

I'm aware of itzg/docker-minecraft-server: Docker image that provides a Minecraft Server that will automatically download selected version at startup (github.com) which makes things pretty easy, but getting any modpack to work still requires quite a bit of fiddling with environment variables (mods to exclude on the server, java version, mc version, enabling command block, etc). Is there something easier, which doesn't require me to search through issues to find working configurations?

Also, as somebody already mentioned, you could run server in a Docker container. I quickly found this: https://hub.docker.com/r/itzg/minecraft-server. You could look into it. For this you will have to setup Docker, but it should be pretty easy (install and add user to group, check Arch wiki). Docker then creates a small "VM" (without kernel) in which Java is installed to run the server itself.

Server is running latest version of PaperMC using the itzg/docker-minecraft-server image on Ubuntu 22.04 LTS. Ports 8123 and 25565 of the container are exposed. Dynmap with LiveAtlas is installed in the server's /plugins/ directory and can be accessed through [server IP]:8123.