Gitea worked on my Synology NAS. Its CI jobs failed before they could check out a single file.

I was hosting Gitea and its Actions runner through Synology Container Manager's Docker Compose support . The server was running, but the runner could not create the container that would execute the workflow. None of the repository's code had run yet.

The fix was to stop running a second Docker daemon inside the runner and use Synology's existing daemon instead. That removed the failing nested mount. It also gave CI access to the same daemon managing the other containers on my NAS. Those are two consequences of the same change.

The Original Compose Configuration

This was the starting configuration. The server had its own persistent data directory, and the runner had both a registration directory and a volume for its inner Docker daemon.…