-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
rhel-sst-container-tools
-
-
-
RUN 228, RUN 229, RUN 230, RUN 232, RUN 233, RUN 234, RUN 235, RUN 236, RUN 237, RUN 238, RUN 239, RUN 240, RUN 241, RUN 242, RUN 243, RUN 244, RUN 245, RUN 246, RUN 247, RUN 248, RUN 249, RUN 250, RUN 251, RUN 252
As a container user, I want to be able to run a custom network driver in Podman so that I can implement my specific network use case.
Containers common needs to be taught how to read/write these.
— FROM DESIGN DOC
Containers common will likely need to be updated to read and write custom configurations. If it finds a driver with an unknown name it must compare it to the installed plugins and throw an error if no plugin with that name is found. If a network should be created, libnetwork should pick an ID and name (if no one was given) for the network. Then it will call the “create” subcommand of the plugin and pass the Network struct as JSON via STDIN and expects as result the same struct on STDOUT.
{
"name": "foobar",
"id": "1217ba07ce3dd4ec54b78e8f1909fabaafd3cc6f008a5ffdb3ac78398aeb56f8",
"driver": "mycustom",
"created": "2022-10-24T13:12:25.80622274-05:00",
"subnets": [
{ "subnet": "192.168.99.0/24", "gateway": "192.168.99.1" }
],
"ipv6_enabled": false,
"internal": false,
"dns_enabled": true,
}
]
Containers common will also need a new field for plugin locations. It will be an array of strings (directory paths).
