Prune volume after update

[mc-supply]

I'm starting to investigate using Watchtower to automate updates. The process works fine as I update my Docker Hub images; it reaches out and updates the local image. However, the volume doesn't change (which makes sense). Following this post: #383, I see it's possible to do a "docker volume prune" as a post update event. When I do this, it executes the command and exits with a 127 error code, and does not do the prune. I tried putting the absolute path to Docker in the command, but continues with the same error. Here is my docker-compose.yml file:

version: "3.4"

services:
    php:
        build:
            context: ./docker/php
        volumes:
            - static-volume:/usr/share/nginx/html
            - ./screen:/screen/
        environment:
            MYSQL_HOST: ${MYSQL_HOST}
            MYSQL_DATABASE: ${MYSQL_DATABASE}
            MYSQL_USER: ${MYSQL_USER}
            MYSQL_PASSWORD: ${MYSQL_PASSWORD}
            BRANCH: ${BRANCH}
            HOST_IP: ${HOST_IP}
        healthcheck:
            test: "php -q /usr/share/nginx/html/health-check.php && php -q /usr/share/nginx/html/sync-files.php"
            interval: 60s
        restart: always
        labels:
        - "com.centurylinklabs.watchtower.enable=false"
    web:
        image: docker.io/mcsupply/tv-display:latest
        ports:
            - "443:443"
        volumes:
            - static-volume:/usr/share/nginx/html
            - ./ssl:/ssl/
            - ./screen:/screen/
        depends_on:
            - php
        restart: always
        labels:
            - "com.centurylinklabs.watchtower.lifecycle.post-update=docker volume prune"
            - "com.centurylinklabs.watchtower.enable=true"
    mysql:
        image: mariadb:latest
        ports:
            - 3306:3306
        depends_on:
            - php
        environment:
            MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
            MYSQL_DATABASE: ${MYSQL_DATABASE}
            MYSQL_USER: ${MYSQL_USER}
            MYSQL_PASSWORD: ${MYSQL_PASSWORD}
        command: --init-file /data/application/init.sql
        volumes:
            - ./init.sql:/data/application/init.sql            
            - mysql-volume:/var/lib/mysql
        restart: always
        labels:
        - "com.centurylinklabs.watchtower.enable=false"        
    watchtower:
        image: index.docker.io/containrrr/watchtower:latest
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock
        command: --interval 30 --debug --remove-volumes --enable-lifecycle-hooks
        labels:
        - "com.centurylinklabs.watchtower.enable=false"        
        restart: always
volumes:
    static-volume:
    mysql-volume:

[zoispag]

Hi there,

afaik hooks are running inside the container. @simskij I see this is your suggestion. Will this work?

I guess you already tried Remove attached volumes flag, right?

[mc-supply]

I'm currently using v3.4, but can probably adjust. I think the use-case is similar enough it may point me in the right direction.

[mc-supply]

I'm attempting to recreate what you did in my environment. So did you do a volume to the codebase in php-fpm, and then use a volumes-from in the nginx container pointing to the codebase in php-fpm? If so, when I update the codebase and Watchtower pulls it down, does it refresh the codebase without requiring a volume prune?

[zoispag]

It’s been a while since I’ve done this. Not 100% sure I used this in production or in dev with mounted volume already, but did you do something similar to the second (v2) example here? Redis is exposing a volume which is then available to the web container.
I still find the 2 containers cleaner as an approach tbh.

[mc-supply]

I ended up just combining PHP and nginx into a single container and not relying on volumes. I know that goes against "best practice", but I'm OK with it for this particular application. Everything with Watchtower is updating properly without needing to prune the volume.

[zoispag]

I know the feeling. In case I find a better alternative (because I am also interested into), I will let you know.

[mc-supply]

I appreciate it! Thank you again for you help.