Mark Dumay

It's a pity that Synology does not support the overlay driver. They tend to heavily modify their distribution, so it doesn't come as a surprise. I came across this [article](https://kristoferlundgren.medium.com/synology-run-the-latest-docker-daemon-without-patching-dsm6-x-7bb4834d87bc)...

@jamescarppe , it seems this is longstanding issue that has to do with Synology's customization of Docker. Issues appear with both regular containers and with a Docker stack deployment. I...

Thanks @bep! I agree the “double” mounting is a bit odd. The module is basically wrapping an existing npm package to modularize it for Hugo. I was trying to avoid...

To add my two cents, I noticed this behavior applies to image resources as well. My site - available in both English (default) and Dutch - contains several pages that...

Thanks for raising the issue. However, to my understanding, `CAP_ADD` is deprecated in favor of `DNSMASQ_LISTENING=all`? The exception is when running Pi-Hole as DHCP server or when using IPv6 Router...

Adding `DNSMASQ_USER: root` to the environment temporarily fixes the privilege error. Use the `develop` branch to add this setting: ```console git clone https://github.com/markdumay/synology-pihole.git -b develop ```

That's odd, it looks like the `acme.sh` script does not pick up the Docker secrets (as staged environment variables) correctly. What happens if you run the following statement from within...

The error seems to be connecting to Synology though? From your logs: ``` acme_1 | [Sun Jun 6 11:36:22 UTC 2021] Logging into xxxxxx:5000 acme_1 | [Sun Jun 6 11:36:28...

It's still strange, I'd expect for the ENV vars to take precedence over the `account.conf` file. Perhaps this has been revised in the `acme.sh` script itself. If I remember correctly,...

I pushed a new development image this morning (or actually, Docker Hub detected a change in the GH repo). The only notable change in the develop branch is the addition...