Installation not possible. start.sh not found

Hi,

i was running a Pi-hole image on a Synology NAS in a Docker Container. After automatic updating by watchtower (Please don't blame me. Lost almost the whole night) the Container stopped and is no longer Starting. Additionally i tried a clean new install even though all settings are lost. It doesnt't work either.

I'm always getting the same error when the Container should be started:

failed to create task for container: failed to create shim task: OCI runtime create failed: 
runc create failed: unable to start container process: exec: "start.sh": executable file not found in $PATH: unknown

The Yaml is pretty much the one from the Installation Example:

More info at GitHub - pi-hole/docker-pi-hole: The official Pi-hole Docker image from pi-hole.net and https://docs.pi-hole.net/

services:
  pihole:
    container_name: piholev6
    image: pihole/pihole:latest
    ports:
      # DNS Ports
      - "53:53/tcp"
      - "53:53/udp"
      # Default HTTP Port
      - "8080:80/tcp"
      # Default HTTPs Port. FTL will generate a self-signed certificate
      - "8443:443/tcp"
      # Uncomment the below if using Pi-hole as your DHCP Server
      #- "67:67/udp"
    environment:
      # Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), e.g:
      TZ: 'Europe/Berlin'
      # Set a password to access the web interface. Not setting one will result in a random password being assigned
      FTLCONF_webserver_api_password: <redacted>
      DNSMASQ_USER: 'root'
    # Volumes store your data between container upgrades
    volumes:
      # For persisting Pi-hole's databases and common configuration file
      - '/volume1/docker/pihole:/etc/pihole'
      # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards
      - '/volume1/docker/pihole/dnsmasq.d-configs:/etc/dnsmasq.d'
    cap_add:
      # See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
      # Required if you are using Pi-hole as your DHCP server, else not needed
      - NET_ADMIN
    restart: unless-stopped

I don't know how to continue. Any help appreciated.

BR
Sascha

Don't do this.