mirror of https://github.com/containers/podman.git
d28e85741f
InfraContainer should go through the same creation process as regular containers. This change was from the cmd level down, involving new container CLI opts and specgen creating functions. What now happens is that both container and pod cli options are populated in cmd and used to create a podSpecgen and a containerSpecgen. The process then goes as follows FillOutSpecGen (infra) -> MapSpec (podOpts -> infraOpts) -> PodCreate -> MakePod -> createPodOptions -> NewPod -> CompleteSpec (infra) -> MakeContainer -> NewContainer -> newContainer -> AddInfra (to pod state) Signed-off-by: cdoern <cdoern@redhat.com> |
||
|---|---|---|
| .. | ||
| pods.go | ||
| types.go | ||
| types_create_options.go | ||
| types_exists_options.go | ||
| types_inspect_options.go | ||
| types_kill_options.go | ||
| types_list_options.go | ||
| types_pause_options.go | ||
| types_prune_options.go | ||
| types_remove_options.go | ||
| types_restart_options.go | ||
| types_start_options.go | ||
| types_stats_options.go | ||
| types_stop_options.go | ||
| types_top_options.go | ||
| types_unpause_options.go | ||