Would there be a way to get runC to start a container without restricting its network access? After reading a little about cgroups I imagine it would be technically possible; but not sure how / if runC would expose this option (or perhaps some other piece of the container running environment if not runC) When using containers for encapsulating development environments; its a frequent use case to not require multiple instances of the container, and being able to interact against it using localhost would be useful.
Thanks, Brent