I just tried downloading & starting the “latest” Debian Docker inside my Synology DS716+ - other images are running fine, so I thought I might give it a try to replace my Raspberry in the future. I am using solely the Synlogy Docker UI. Not the console ATM.
Downloading is fine (as it should be). When creating a new container I chose the default values without touching anything. Vanilla, you could say. Starting the container is fine until the web interface seems to be prepared.
Does anybody know whether the current 2.5.0 image currently has issues? Or did I forget to set up anything? As I said: I am not linking internal directories to an external ones.
I’ve been running OH in Docker for years and have experienced no similar problems. But I don’t run on Synology and I know many have difficulty doing so.
Running OH in Docker on Synology for some time without any issues. Have never seen this log messages. But I have to admit I’m still an m5 and not the latest release. What exactly is the command you used to start the container?
Maybe you’ll have better luck starting the container from the console. When it is started you can still use the Synology UI to interact with the container. I had luck with the following docker-compose.yml file: