Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
nrm
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • argo
  • nrm
  • Issues
  • #18

Closed
Open
Opened Oct 21, 2018 by Swann Perarnau@perarnau
  • Report abuse
  • New issue
Report abuse New issue

Split container management from the management of running processes

Merges !27 (merged) and !28 (merged) made pretty obvious that we have a problem with the way we manage the processes running inside containers. I would recommend that we start thinking about a way to avoid tracking processes inside the container manager, as a way to clean up our signal/io/cleanup code.

As a first obvious issue, note that !27 (merged) introduced a problem with commands running in existing containers not waiting for all of their IO (@sriduttb, be mindful of that during future experiments).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: argo/nrm#18