Move container params building to shim #3

Closed
opened 2025-08-19 11:34:40 +09:00 by ophestra · 2 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
Author
Owner

This should not break the API as it is internal to the implementation. Getting this implemented will take a lot of time and effort, so unfortunately this is not making it into v0.2.0.

This should not break the API as it is internal to the implementation. Getting this implemented will take a lot of time and effort, so unfortunately this is not making it into v0.2.0.
ophestra removed this from the v0.2.0 milestone 2025-08-26 01:57:50 +09:00
Author
Owner

Everything is almost in place for this to happen. Adding this to v0.3.0.

Everything is almost in place for this to happen. Adding this to v0.3.0.
ophestra added this to the v0.3.0 milestone 2025-09-29 06:53:19 +09:00
cat closed this issue 2025-10-08 22:42:15 +09:00
Sign in to join this conversation.
No description provided.