Mark Dumay

Thanks for sharing your findings @frobnicaty - that's some serious research! Looking forward to your continued investigation.

I agree with your concern, it wouldn't be great to suddenly have your NAS fully exposed to the public internet. It's quite a challenging subject, as Docker messes with the...

Hi @1activegeek, I added preliminary support for your request in the `develop` branch. I haven't thoroughly tested it yet (and I'm about to go offline for a few days ;-)...

For those interested, I ran into this [gist](https://gist.github.com/PedroLamas/db809a2b9112166da4a2dbf8e3a72ae9) by @pedrolamas. I haven't tested it myself yet, but it seems worth looking into.

Thanks for the heads up @pedrolamas! I was indeed curious about the reason behind your script. I'm running Pi-Hole on my NAS - eager to find out if your script...

Cool! It probably won't solve the networking issues mentioned in this issue thread then - I'll create a new issue in this [repository](https://github.com/markdumay/synology-pihole) instead ;-).

Hi @CardcaptorRLH85, sorry to hear about your issues. Luckily you were able to restore the Docker engine to its original state. The log file and configuration all look normal to...

Thanks for the follow up @CardcaptorRLH85. > I'm using Btrfs. The `btrfs` support seems to questionable (see #22). My NAS uses `ext4`, so I haven't found a way to test...

The storage driver seems to be a tough one to fix. Docker's [documentation](https://docs.docker.com/storage/storagedriver/select-storage-driver/) provides some additional clues. If you have the time and patience, you could try alternative storage drivers...

Does `/var/log/upstart/pkg-Docker-dockerd.log` provide any clues?