3 ms·
> you need to expose your docker socket to the container I always thought this was a hard limitation, but I deployed some self-hosted GHA runners in Kubernetes
by bo0tzz 3y ago
> you need to expose your docker socket to the container
I always thought this was a hard limitation, but I deployed some self-hosted GHA runners in Kubernetes this week and to my surprise that setup came with an option to run the full docker daemon inside of a container - so apparently it is possible.
- alexellisuk 3y agoIf you're running a full docker daemon, then you'll be running as a privileged container which is worse or about the same in terms of terms of poor security. Anyone's workload can compromise the host, and likely the cluster. Rootless containers are a lot of work and do not support many scenarios that you're going to need. MicroVMs are the same experience as GitHub, full system and Kernel, do what you will. Even launch a nested VM.