Docker has found its way in simplifying the Unix fork/exec daemon paradigm through creating contained processes, and restricting communication between these via the daemon running on the host kernel.
This is old technology existing for over 40 years, that is as old as Unix ( Thanks Kernigan and Richie, seriously its not a prank,in spite of rumour, although there are times when it appears to be, obscure as it is ).
Docker daemon packages fork/exec, share memory, thus obviating the need for shared or local library creation, which anyone working with Unix will admit has many variants and is complex to implement in parallel processing scenarios. One needs to be the master of the “makefile” to get this right in the traditional sense, and honestly who cares? Interesting.
Given the difficulties in sharing IPC space within Docker wouldn’t it be easier to just write some IPC code libraries ?