Move container params building to shim #3

Open
opened 2025-08-19 11:34:40 +09:00 by ophestra · 0 comments
Owner

Currently container params are built while the outcome is being finalised, then transmitted to shim. This not only introduces unnecessary IPC overhead but also makes testing slightly more difficult due to the container params being tied to the OS library stub.

A better alternative would be to transmit a set of resolved paths and options to the shim, and have the shim build the final container params.

Currently container params are built while the outcome is being finalised, then transmitted to shim. This not only introduces unnecessary IPC overhead but also makes testing slightly more difficult due to the container params being tied to the OS library stub. A better alternative would be to transmit a set of resolved paths and options to the shim, and have the shim build the final container params.
ophestra added this to the v0.2.0 milestone 2025-08-19 11:34:40 +09:00
ophestra added the
enhancement
label 2025-08-19 11:34:40 +09:00
Sign in to join this conversation.
No description provided.