mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-12 18:47:50 +00:00
0630d19b34
In `podman inspect` output for containers and pods, we include the command that was used to create the container. This is also used by `podman generate systemd --new` to generate unit files. With remote podman, the generated create commands were incorrect since we sourced directly from os.Args on the server side, which was guaranteed to be `podman system service` (or some variant thereof). The solution is to pass the command along in the Specgen or PodSpecgen, where we can source it from the client's os.Args. This will still be VERY iffy for mixed local/remote use (doing a `podman --remote run ...` on a remote client then a `podman generate systemd --new` on the server on the same container will not work, because the `--remote` flag will slip in) but at the very least the output of `podman inspect` will be correct. We can look into properly handling `--remote` (parsing it out would be a little iffy) in a future PR. Signed-off-by: Matthew Heon <matthew.heon@pm.me> <MH: Fixed build after cherry-pick> Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
|---|---|---|
| .. | ||
| annotations | ||
| api | ||
| auth | ||
| autoupdate | ||
| bindings | ||
| cgroups | ||
| channelwriter | ||
| checkpoint | ||
| criu | ||
| ctime | ||
| domain | ||
| env | ||
| errorhandling | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| lookup | ||
| namespaces | ||
| netns | ||
| network | ||
| parallel | ||
| ps | ||
| registrar | ||
| registries | ||
| resolvconf | ||
| rootless | ||
| rootlessport | ||
| seccomp | ||
| selinux | ||
| signal | ||
| spec | ||
| specgen | ||
| systemd | ||
| terminal | ||
| timetype | ||
| tracing | ||
| trust | ||
| util | ||
| varlink | ||
| varlinkapi | ||