Fine-grained seccomp profile managed by Backend.AI Agent

[kyujin-cho]

Main idea

Since it is well known that some newly released accelerators rely on bleeding-edge syscalls, which are often blocked by docker's default seccomp profile for various reasons. To deal with such issues we can think of a serial of ideas:

• Add a copy of Docker's latest seccomp profile JSON into Backend.AI Agent's distribution artifact
• Add a new interface to AbstractAccelerator which tells set of syscalls to be allowed inside container
  • scratch directory fits good to store the file
• Each time kernel spawns make Agent create a copy of the profile JSON and utilizes it as a new seccomp profile JSON for the container
• If the attached accelerator requires extra syscalls to operate (which are determined by step 2) alter the single-use seccomp profile to allow it

Alternative ideas

No response

Anything else?

No response