Skip to content

Conversation

jsturtevant
Copy link
Contributor

Because the second invocation of the shim doesn't have the containerd pipe passed to it, a shim that wants to communicate over the pipe needs to parse the arguments its own. This makes it so the library pass all the arguments, which has already parsed the arguments allowing shims to use the containerd address.

This came up in runwasi: containerd/runwasi#147 (review)

@mxpv
Copy link
Member

mxpv commented Jun 29, 2023

@jsturtevant could you pls resolve conflicts?
This should be good to merge once green.

Because the second invocation of the shim doesn't have the containerd pipe passed to it, a shim that wants to communicate over the pipe needs to parse the arguments its own.  This makes it so the library pass all the arguments, which has already parsed the arguments allowing shims to use the containerd address.

Signed-off-by: James Sturtevant <[email protected]>
@jsturtevant
Copy link
Contributor Author

@mxpv updated, sorry for the delay was away from the computer for awhile!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-shim Containerd shim
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants