If you’re running forgejo runner in a docker container, it can only do things inside that container (excepting if it connects to something else). You could give that container access to the docker daemon, but at that point it’s effectively a privileged runner with root access, and I don’t think I would want to do that.
If you install forgejo runner on the host itself and give it access to the docker daemon, it could run docker compose up, but otherwise it’s trying to use an asset that it cannot access.
You could also feasibly have the runner SSH into the target machine and run docker commands from there.
To me, both of these are suboptimal and I would sooner split the job into two phases:
If you’re running forgejo runner in a docker container, it can only do things inside that container (excepting if it connects to something else). You could give that container access to the docker daemon, but at that point it’s effectively a privileged runner with root access, and I don’t think I would want to do that.
If you install forgejo runner on the host itself and give it access to the docker daemon, it could run docker compose up, but otherwise it’s trying to use an asset that it cannot access.
You could also feasibly have the runner SSH into the target machine and run docker commands from there.
To me, both of these are suboptimal and I would sooner split the job into two phases: