Enable memory, cpu, and other limits on the container

[tfoote]

Docker allows the restriction of memory allocation from inside the container. This is valuable to make sure that containers don't potentially overflow a host's memory.

https://docs.docker.com/config/containers/resource_constraints/

[Yongbeom-Kim]

Hey @tfoote thanks for maintaining rocker, mind if i work on this?

[tfoote]

You're welcome. I'm happy to take contributions. If you have a good idea of how to implement this you can go ahead though I'd recommend a sketch of your approach first, or I'd be happy to talk with you about the best approach before you start an implementation.

[Yongbeom-Kim]

Sounds good,

The implementation sounds pretty simple at a technical level - entails essentially 'forwarding' the 10-or-so flags for docker run?

Can't say I'm super thrilled about writing N RockerExtension classes that basically do the same thing. I'm thinking a metaclass or a function to dynamically create these class instances would be perfect - your thoughts?

[tfoote]

One plugin can offer different command line options. I think that a single plugin that implements the different capacity based arguments would make sense. As long as the underlying dependencies and requirements are the same if you can share code resources that's better. I think the primary thing will be the availability of cgroups support which will likely be a shared dependency and validation check.