mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-24 01:07:53 +00:00
some platforms and operating systems do not have varlink. in those cases, we need to be able to turn off enablement of varlink in podman. this can now be done with BUILDTAGS passed to the build though perhaps in the future will be better. the default is to build with varlink Signed-off-by: baude <bbaude@redhat.com> squash! make varlink optional for podman The API.md and cmd/podman/varlink/ioprojectatomicpodman.go targets will continue to work regardless of the presence (or not) of 'varlink' is in BUILDTAGS. However, cmd/podman/varlink/ioprojectatomicpodman.go is now only required by the podman target when BUILDTAGS contains 'varlink'. API.md had also been an podman dependency since |
||
|---|---|---|
| .. | ||
| batchcontainer | ||
| docker | ||
| formats | ||
| libpodruntime | ||
| varlink | ||
| attach.go | ||
| build.go | ||
| commit.go | ||
| common.go | ||
| common_test.go | ||
| container.go | ||
| create.go | ||
| create_cli.go | ||
| create_cli_test.go | ||
| diff.go | ||
| exec.go | ||
| export.go | ||
| history.go | ||
| image.go | ||
| images.go | ||
| import.go | ||
| info.go | ||
| inspect.go | ||
| kill.go | ||
| load.go | ||
| login.go | ||
| logout.go | ||
| logs.go | ||
| main.go | ||
| mount.go | ||
| parse.go | ||
| pause.go | ||
| port.go | ||
| ps.go | ||
| pull.go | ||
| push.go | ||
| README.md | ||
| refresh.go | ||
| restart.go | ||
| rm.go | ||
| rmi.go | ||
| run.go | ||
| run_test.go | ||
| save.go | ||
| search.go | ||
| sigproxy.go | ||
| start.go | ||
| stats.go | ||
| stop.go | ||
| tag.go | ||
| top.go | ||
| umount.go | ||
| unpause.go | ||
| user.go | ||
| utils.go | ||
| varlink.go | ||
| varlink_dummy.go | ||
| version.go | ||
| wait.go | ||
podman - Simple debugging tool for pods and images
podman is a daemonless container runtime for managing containers, pods, and container images. It is intended as a counterpart to CRI-O, to provide low-level debugging not available through the CRI interface used by Kubernetes. It can also act as a container runtime independent of CRI-O, creating and managing its own set of containers.
Use cases
- Create containers
- Start, stop, signal, attach to, and inspect existing containers
- Run new commands in existing containers
- Push and pull images
- List and inspect existing images
- Create new images by committing changes within a container
- Create pods
- Start, stop, signal, and inspect existing pods
- Populate pods with containers