Kathryn Baldauf 9032d73d07 Change behavior of the default arguments in the plugin config (#1063) ...

## Type of Change
- [x] New feature  
- [x] Breaking change

## Motivation and Context
This PR changes the behavior of the `defaultArguments` field in the
service plugin config. Previously, `defaultArguments` was functioning as
a way to indicate how to start a plugin in the event that the plugin is
loaded at boot (such as for the `container-core-images plugin`).
However, we now follow a convention where all plugins have a "start"
command that is used when launching the plugin, so this
`defaultArguments` field wasn't really providing much. Instead, there
are use cases where we may want to set default values to pass to a
plugin. This PR repurposes the `defaultArguments` field for those use
cases.

As an example use case, there are scenarios where someone may want to
use the AllocationOnlyVmnetNetwork even when running on macOS 26+. This
PR adds the ability to pass in a command line option to the vmnet
network plugin to specify that request. Combined with the
`defaultArguments` plugin config change, a user may choose to set that
field to ["--variant", "allocationOnly"] in the
`container-network-vmnet-config.json` to use AllocationOnlyVmnetNetwork
by default for all networks.

## Testing
- [x] Tested locally

2026-01-19 19:22:55 -08:00

..

container-core-images-config.json

Change behavior of the default arguments in the plugin config (#1063)

2026-01-19 19:22:55 -08:00

container-network-vmnet-config.json

Initial commit

2025-06-05 15:51:55 -07:00

container-runtime-linux-config.json

SandboxService: Turn off RunAtLoad for the default plugin (#649)

2025-09-19 08:56:12 -07:00