shepherd VS cioban

Since watchtower doesn't support Docker Swarm I've come across shepherd but the author has stated that he wont be maintaining the project anymore which makes me reluctant to use it.

Shepherd for those of that run docker swarm.

Not at production (there are strict versioned images), but personally I use Shepherd in my distributed Docker Swarm (many hosts in different locations, even different architectures). I wonder why people say about some terrible issues. I must be very lucky: for over a year usage I've had only single one problem when service wasn't properly restarted (I remember it was Traefik). The only services excluded from auto-update are PostgreSQL and MongoDB (MariaDB works fine with auto updates).

Because all my Docker services are running in Docker Swarm I use similar project shepherd (available also at dockerhub). Not many features, but extremely easy to set up and it does its job (check, download and restart any service when new image is available, so I don't need to care about program updating at all).

I've used this for years

I'm the developer of cioban, that started off as a shepherd clone, but was rewritten in python. I have it both at home and at work (where we can pull off with unattended upgrades of certain containers).

Mentioning this, because I had a container on my rpi that crashed about once per week - once I switched to swarm I never had to touch it again (since I was using also cioban - which I developed as an alternative to watchtower, that actually runs on docker swarm).

The relevant portion is on line #L96: sh docker buildx build --platform=linux/amd64,linux/arm64,linux/arm/v7,linux/arm/v6 --progress=plain --cache-from=registry.gitlab.com/ix.ai/cioban:cache --cache-to=registry.gitlab.com/ix.ai/cioban:cache --build-arg CI_COMMIT_REF_NAME=master --build-arg CI_PIPELINE_ID=272907066 --pull --tag=registry.gitlab.com/ix.ai/cioban:dev-master --tag=ixdotai/cioban:dev-master --tag=ghcr.io/ix-ai/cioban:dev-master --push .