Docker: certs renewed but not deployed to container

[kinslayer1982]

I set up acme.sh Docker container alongside my HAProxy container to manage my certificates. I added

labels:
    - sh.acme.autoload.domain=xxx.xxx

to my HAProxy container and

volumes:
    - /var/run/docker.sock:/var/run/docker.sock
environment:
    - DEPLOY_DOCKER_CONTAINER_LABEL=sh.acme.autoload.domain=xxx.xxx
    - DEPLOY_DOCKER_CONTAINER_KEY_FILE=/xxx/certs/xxx.xxx.key
    - DEPLOY_DOCKER_CONTAINER_CERT_FILE="/xxx/certs/cert.pem"
    - DEPLOY_DOCKER_CONTAINER_CA_FILE="/xxx/certs/ca.pem"
    - DEPLOY_DOCKER_CONTAINER_FULLCHAIN_FILE="/xxx/certs/fullchain.pem"
    - DEPLOY_DOCKER_CONTAINER_RELOAD_CMD="pkill -SIGUSR2 haproxy"

to the acme.sh container.

Some time later my devices refused to connect to my services caused by an expired certificate. When I checked the certificate had been renewed the certificate files on the host machine were the correct new ones. So I checked the reload command to verify it is working and it is correct. Still the container was using the old certificate.

Is it possible that this way of deploying certificates to containers conflicts with bind mounts somehow?

[github-actions]

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

[kinslayer1982]

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

According to the official instructions that would mean issuing the command docker exec acme.sh --debug which only results in an unknown command error while docker exec acme.sh --version, --list, --info, etc do work.