while we can intercept calls using a shim library in programs running on a traditional linux server, sometimes code arrives that meant to be deployed as an opaque binary container. It could be impractical to insert the shared library into containers like that, and it might be a lot more elegant to use container mechanisms instead.
reading materials:
So... the gist is that we might be able to use bpf filtering around containers, usually used for security, to intercept calls to underlying disks, and map the calls to the existing libsr3shim, or something very like it, to create posts of files written by the container.
while we can intercept calls using a shim library in programs running on a traditional linux server, sometimes code arrives that meant to be deployed as an opaque binary container. It could be impractical to insert the shared library into containers like that, and it might be a lot more elegant to use container mechanisms instead.
reading materials:
So... the gist is that we might be able to use bpf filtering around containers, usually used for security, to intercept calls to underlying disks, and map the calls to the existing libsr3shim, or something very like it, to create posts of files written by the container.