Matt The Horwood

I run swarm in my homelab and have done for years, traefik runs on my manager and uses the docker swarm networks to get to services.

My traefik compose makes all the service networks, then each service compose has an external network that all the containers connect to.

This is my example config, this might help - https://github.com/mhzawadi/docker-stash/tree/master/swarm

Also learn to search man pages, you might get a wall of text. But a search will jump you to what your looking for

man is just less

You don’t need to pipe in to grep, use a / to search it.

Man ps

/user enter

Then use n to find the next instance of the search

you could use shell scripts, but that might get very complex very quick, thats where ansible comes in. you make a playbook with the tasks to get a server from vanilla OS to how you want it.

tasks can do anything from install a package (with yum or apt or dnf) to uploading files and everything else you might need, the docs are quite good and have good examples.

As a user for about 9 years, both homelab and work. It can be overwhelming at first, but then you start to see why its used so much.

it looks like a unix system enough that I can run most of my shell scripts, Windows on the other hand can get in the bin please

Looking at the docs, I think the current docker desktop is native arm. QEMU is now deprecated

I see, I don’t use docker all that much on my works Mac. So haven’t noticed the speed.

Also is it the storage share that’s slow? As docker desktop is a VM

Why do you need WSL?

MacOS is BSD, so you can do most Linux things with an issue. But some of the BSD tools have different options the the GNU tools.

We moved to Mac years ago and it makes doing almost everything I do a simples

I have been using OVH for years now, both VPS and dedicated hosts. The VPS offerings are all unmetered!

asciiquarium?

Watching him, makes me think I should do videos of stuff I know. But not found the want yet

the first step is workout what you did, what did you install and where from. Then what config files got edited.

Much like a playbook for a disaster recovery test

Next is using some of the builtin modules like package and copy, make a very noddy playbook that will install stuff and copy up the config. if you have vms, you can use a test vm to see if the playbook works.

If you’ve not played ansible than this might help 👉 https://www.jeffgeerling.com/project/ansible-101-youtube-series

Hello you maybe best do some reading up on how ansible works, as it can get very complex.

This might be a good sting point 👉 https://www.jeffgeerling.com/project/ansible-101-youtube-series

There’s some really good options in this thread, just remember that whatever you pick. Unless you test your backups, they are as good as not existing.

also Ubuntu will add more complexity to things, Debian will cover most of what you need.