Container feature is not supported when runner is already running inside container.

Question

Container feature is not supported when runner is already running inside container.

ScottPierce opened this issue 4 years ago · comments

I already saw #42

My question is - how is everyone not running into this? It seems like this is a restriction for all OS?
https://github.com/actions/runner/blob/f9b5d626c5486d1f02b3bd45879f61834b7aeecc/src/Runner.Worker/ContainerOperationProvider.cs#L57-L70

The docker runner seems pointless if we can't launch other containers from it. Can someone else describe how they have this working so that I can emulate it?

myoung34 · Answer 1 · Thu Oct 15 2020 03:21:03 GMT+0800 (China Standard Time)

how is everyone not running into this?

Not every workflow kicks off docker

To be honest your best bet is to try and make progress on getting upstream support for actions/runner#406

Bret Fisher · Answer 2 · Sat Jul 17 2021 05:10:57 GMT+0800 (China Standard Time)

Yep, same issue. Tried to add an Actions Service to a job, and got this error. It checks cgroups, so I don't see a hacky way around it (other then not using Job Services).

I'll submit a PR to highlight this limitation at the top of the readme so someone doesn't spend time trying to implement this container image, only to find out later it limits GHA functionality.

myoung34 · Answer 3 · Sat Jul 17 2021 05:14:31 GMT+0800 (China Standard Time)

@BretFisher It's documented here

Bret Fisher · Answer 4 · Sat Jul 17 2021 05:17:40 GMT+0800 (China Standard Time)

Yea, but I read that as saying "docker isn't officially supported by GitHub as a way to run runners", not "using this image will limit GHA functionality" so hopefully that clarification helped. Thanks for all you do.