Skip to content
This repository was archived by the owner on Nov 8, 2024. It is now read-only.
This repository was archived by the owner on Nov 8, 2024. It is now read-only.

setting resource limits causes bad behavior for unprivileged containers #11

@xmcqueen

Description

@xmcqueen

I've started working on this. It looks to be not very active. I'm wondering about the state of this plugin. I'm working on getting it going for unprivileged containers. Its working at this point, but I want to take it further.

I noticed when I use the existing plugin's setResourceLimits, I get some odd behavior. One of which is when I add resource limits, the plugin starts the unprivileged containers, and then starts a whole new set of privileged ones.

I'm looking for warnings or advice from any maintainers, since I'm about to push ahead and make this work.

  • Is this plugin designed to run as root and do only privileged containers?
  • If so should I try to make it do both privileged and unprivileged or should I just go rogue

I've got some related questions about the design assumptions, so I guess if there are any maintainers I'd like to chat.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions