Jean-Yves
Jean-Yves
Don't worry, i'll handle it.
Solved and up to date and ready (to be tested anyway...)
I have podman on my machine and I can't launch the container... I can't test it and I don't have time to debug...
> Why may I ask? Do you run into an issue here? ```shell podman run \ --rm \ --name nextcloud-aio-mastercontainer \ --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config:z \ --volume /var/run/user/1000/podman/podman.sock:/var/run/docker.sock:z \ --env WATCHTOWER_DOCKER_SOCKET_PATH=/var/run/user/1000/podman/podman.sock \...
 :roll_eyes: :roll_eyes: :roll_eyes: :roll_eyes: thank :sweat_smile:
It doesn't work, I give up. Can you test this? One way to test would be to go into the Nextcloud container and add `exit 1` in the `heathcheck.sh` script....
Another question Why not use `starting` state and `restarting` state from docker ? > Enum: "created" "running" "paused" "restarting" "removing" "exited" "dead" > > String representation of the container state....
Docker doc for meaning of state https://docs.docker.com/reference/cli/docker/container/ls/#status
A proposal in commit b903cc3. (I renamed the enums to match the getters name, it's more consistent but I can rollback)
> A proposal in commit b903cc3. What do you think @szaimen ?