

It’s definitely a valid concern. I connected a device between it and the rest of my network and spent some time recording anything it sent. I wasn’t able to find any telemetry at all. I also keep it segregated from the rest of my network by vlan, and it only has a few specific routes to reach my self hosted services.
I do, however, want to point out that a chromecast is going to have a ton of telemetry. It’s hard to be truly certain of any devices these days, but I spent some time digging into the OS and I’m pretty confident that it’s truly my device.
I don’t use google cast, but I’m fairly sure it could if I used it. It has a remote, so I just use that. If I want to use jellyfin, or whatever app, I just install it on the device and log straight in. I don’t use mine as a portable stick like you mentioned. It’s intended to turn a dumb tv into a smart tv, and that’s all I want it to do.

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: