Could someone please help with how I'm meant to set a docker container up to use Autoheal?

Autoheal is set as AUTOHEAL_CONTAINER_LABEL=heal

My dockers containers I want to watch have:

AUTOHEAL_CONTAINER_LABEL=heal

I'm not sure if this is correct as the Github states AUTOHEAL_CONTAINER_LABEL: autoheal-app

Logs for auto heal show:

AUTOHEAL_CONTAINER_LABEL=heal

AUTOHEAL_START_PERIOD=0

AUTOHEAL_INTERVAL=5

AUTOHEAL_DEFAULT_STOP_TIMEOUT=10

AUTOHEAL_ONLY_MONITOR_RUNNING=false

compose or env?

for what dockers?

Docker within the UnRaid WebUI.

Again, this is for various dockers all created within the WebUI.

This is using the below App.

https://github.com/willfarrell/docker-autoheal/issues

you either need to run the docker run from and hav the "autoheal docker running" per the github page or you need to add additional labels simalr to the watch tower docker(autoupdate) to the dockers you want it to work on and affect...

Docker Autoheal

Monitor and restart unhealthy docker containers. This functionality was proposed to be included with the addition of HEALTHCHECK, however didn't make the cut. This container is a stand-in till there is native support for --exit-on-unhealthy moby/moby#22719.

2. Use in your container image

Choose one of the three alternatives:

a) Apply the label autoheal=true to your container to have it watched;
b) Set ENV AUTOHEAL_CONTAINER_LABEL=all to watch all running containers;
c) Set ENV AUTOHEAL_CONTAINER_LABEL to existing container label that has the value true;

Note: You must apply HEALTHCHECK to your docker images first.
See https://docs.docker.com/engine/reference/builder/#healthcheck for details.

Docker Compose (example)

services:
  app:
    extends:
      file: ${PWD}/services.yml
      service: app
    labels:
      autoheal-app: true

  autoheal:
    deploy:
      replicas: 1
    environment:
      AUTOHEAL_CONTAINER_LABEL: autoheal-app
    image: willfarrell/autoheal:latest
    network_mode: none
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock

so again what is it that your trying to do? ...

whats the isseus. what are you tryign to do ...

liek add autohela to a template docker???

You may need to go into advance view...

and add somethign here:

or by adding somehtign to the template...

again per the github:

cuz at best this just runs ontop of the docker /var runtime socket adding a healthcheck like process to dockers taht may or may not have a health check to stop unhealty dockers...

Makes more sense to run this with compose... Regardless you ned 1 master Docker running - can be ran directly form the github and let it do its thing or add adational lables and option to the other dockers.
review:

Watch tower
https://www.youtube.com/watch?v=mSSlrRgSAP4

More about health Cheks and docker:

https://www.youtube.com/watch?v=yBJ2baG-ULY

and implemeting health check to a docker:
https://www.youtube.com/watch?v=_CVewEfVQAo

Unraid is not helm, kubernetes or docker in a docker swam... its barley podman depending on interactions. and you get more out of health checks and this auto heal if you run portainer ontop of unraid to view the health and other image of a docker.

I see no value or usecase with this auto heal docker on unraid.

as this is simlar to watch tower. you run the auto heal dokcer. that will restart a docker is its unhealthy

Idelay the master check auto hela docker run and is set to use the label

any docker you want to have auto heal gets a new environment variable

-e AUTOHEAL_CONTAINER_LABEL=true

so whats the issue? how to add to unraid in gerneral? or how to use with a exisitng docker / application stack?

as unraid has simalr default options to killl and stop a docker non functional and simalr things can be scripted and used with portainer and proper healthcheck where the docker doesn't kill but internal services restart.

esentail you have to ask what make the dockeer unhealthy. and whne does it need to restart.

Helath check can be mis represneted and fail marking a docker as unhealthy. that doen't mean a restart will fix the issue...