CLI and API mismatch

[shotor]

Introduced by #1298 - unreleased

--entrypoint can no longer represent an OCI entrypoint argv array

Microsandbox internally uses Vec<String>, but the CLI exposes --entrypoint as a single String. If you now run:

msb run --entrypoint '/bin/sh -c echo foo; exec something'

It creates a single entrypoint argv element rather than preserving the original argv.

Would it make sense for --entrypoint to be repeatable, accept an argv representation, or otherwise expose the same semantics as the underlying API?

Context

I ran into this by using microsandbox main branch with devsy. #1298 is an intentional breaking behavior change for cli consumers. msb create currently causes the configured workload/entrypoint to execute, while after this change it's boot-only. Existing integrations that depended on that behavior will after this change successfully create a running sandbox, but without their expected workload being started.

Migrating devsy to use msb run --detach exposed the separate --entrypoint argv issue described above.

I've also created an issue at devsy: devsy-org/devsy#1035

As well as a PR: devsy-org/devsy#1036

[appcypher]

you could do msb run ... -- sh -c "echo foo; exec something".

although i agree we should make sth like this work.

msb run --entrypoint '/bin/sh -c echo foo; exec something'