github.com/hanks177/podman/v4@v4.1.3-0.20220613032544-16d90015bc83/docs/source/markdown/podman-remote.1.md (about) 1 % podman-remote(1) 2 3 ## NAME 4 podman-remote - A remote CLI for Podman: A Simple management tool for pods, containers and images. 5 6 ## SYNOPSIS 7 **podman-remote** [*options*] *command* 8 9 ## DESCRIPTION 10 Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool. 11 Podman provides a Docker-CLI comparable command line that eases the transition from other 12 container engines and allows the management of pods, containers and images. Simply put: `alias docker=podman`. 13 Most Podman commands can be run as a regular user, without requiring additional 14 privileges. 15 16 Podman uses Buildah(1) internally to create container images. Both tools share image 17 (not container) storage, hence each can use or manipulate images (but not containers) 18 created by the other. 19 20 Podman-remote provides a local client interacting with a Podman backend node through a RESTful API tunneled through a ssh connection. In this context, a Podman node is a Linux system with Podman installed on it and the API service activated. Credentials for this session can be passed in using flags, environment variables, or in `containers.conf`. 21 22 The `containers.conf` file should be placed under `$HOME/.config/containers/containers.conf` on Linux and Mac and `%APPDATA%\containers\containers.conf` on Windows. 23 24 **podman [GLOBAL OPTIONS]** 25 26 ## GLOBAL OPTIONS 27 28 #### **--connection**=*name*, **-c** 29 30 Remote connection name 31 32 Overrides environment variable `CONTAINER_CONNECTION` if set. 33 34 #### **--help**, **-h** 35 36 Print usage statement 37 38 #### **--identity**=*path* 39 40 Path to ssh identity file. If the identity file has been encrypted, Podman prompts the user for the passphrase. 41 If no identity file is provided and no user is given, Podman defaults to the user running the podman command. 42 Podman prompts for the login password on the remote server. 43 44 Identity value resolution precedence: 45 - command line value 46 - environment variable `CONTAINER_SSHKEY`, if `CONTAINER_HOST` is found 47 - `containers.conf` 48 49 #### **--log-level**=*level* 50 51 Log messages above specified level: debug, info, warn, error (default), fatal or panic 52 53 #### **--url**=*value* 54 55 URL to access Podman service (default from `containers.conf`, rootless "unix://run/user/$UID/podman/podman.sock" or as root "unix://run/podman/podman.sock). 56 57 - `CONTAINER_HOST` is of the format `<schema>://[<user[:<password>]@]<host>[:<port>][<path>]` 58 59 Details: 60 - `schema` is one of: 61 * `ssh` (default): a local unix(7) socket on the named `host` and `port`, reachable via SSH 62 * `tcp`: an unencrypted, unauthenticated TCP connection to the named `host` and `port` 63 * `unix`: a local unix(7) socket at the specified `path`, or the default for the user 64 - `user` will default to either `root` or the current running user (`ssh` only) 65 - `password` has no default (`ssh` only) 66 - `host` must be provided and is either the IP or name of the machine hosting the Podman service (`ssh` and `tcp`) 67 - `port` defaults to 22 (`ssh` and `tcp`) 68 - `path` defaults to either `/run/podman/podman.sock`, or `/run/user/$UID/podman/podman.sock` if running rootless (`unix`), or must be explicitly specified (`ssh`) 69 70 URL value resolution precedence: 71 - command line value 72 - environment variable `CONTAINER_HOST` 73 - `containers.conf` `service_destinations` table 74 - `unix://run/podman/podman.sock` 75 76 Remote connections use local containers.conf for default. 77 78 Some example URL values in valid formats: 79 - unix://run/podman/podman.sock 80 - unix://run/user/$UID/podman/podman.sock 81 - ssh://notroot@localhost:22/run/user/$UID/podman/podman.sock 82 - ssh://root@localhost:22/run/podman/podman.sock 83 - tcp://localhost:34451 84 - tcp://127.0.0.1:34451 85 86 #### **--version** 87 88 Print the version 89 90 ## Environment Variables 91 92 Podman can set up environment variables from env of [engine] table in containers.conf. These variables can be overridden by passing environment variables before the `podman` commands. 93 94 #### **CONTAINERS_CONF** 95 96 Set default locations of containers.conf file 97 98 #### **CONTAINER_CONNECTION** 99 100 Set default `--connection` value to access Podman service. 101 102 #### **CONTAINER_HOST** 103 104 Set default `--url` value to access Podman service. 105 106 #### **CONTAINER_SSHKEY** 107 108 Set default `--identity` path to ssh key file value used to access Podman service. 109 110 ## Exit Status 111 112 The exit code from `podman` gives information about why the container 113 failed to run or why it exited. When `podman` commands exit with a non-zero code, 114 the exit codes follow the `chroot` standard, see below: 115 116 **125** The error is with podman itself 117 118 $ podman run --foo busybox; echo $? 119 Error: unknown flag: --foo 120 125 121 122 **126** Executing a _contained command_ and the _command_ cannot be invoked 123 124 $ podman run busybox /etc; echo $? 125 Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error 126 126 127 128 **127** Executing a _contained command_ and the _command_ cannot be found 129 $ podman run busybox foo; echo $? 130 Error: container_linux.go:346: starting container process caused "exec: \"foo\": executable file not found in $PATH": OCI runtime error 131 127 132 133 **Exit code** _contained command_ exit code 134 135 $ podman run busybox /bin/sh -c 'exit 3'; echo $? 136 3 137 138 139 ## COMMANDS 140 141 | Command | Description | 142 | ------------------------------------------------ | --------------------------------------------------------------------------- | 143 | [podman-attach(1)](podman-attach.1.md) | Attach to a running container. | 144 | [podman-build(1)](podman-build.1.md) | Build a container image using a Dockerfile. | 145 | [podman-commit(1)](podman-commit.1.md) | Create new image based on the changed container. | 146 | [podman-container(1)](podman-container.1.md) | Manage containers. | 147 | [podman-cp(1)](podman-cp.1.md) | Copy files/folders between a container and the local filesystem. | 148 | [podman-create(1)](podman-create.1.md) | Create a new container. | 149 | [podman-diff(1)](podman-diff.1.md) | Inspect changes on a container or image's filesystem. | 150 | [podman-events(1)](podman-events.1.md) | Monitor Podman events | 151 | [podman-export(1)](podman-export.1.md) | Export a container's filesystem contents as a tar archive. | 152 | [podman-generate(1)](podman-generate.1.md) | Generate structured data based for a containers and pods. | 153 | [podman-healthcheck(1)](podman-healthcheck.1.md) | Manage healthchecks for containers | 154 | [podman-history(1)](podman-history.1.md) | Show the history of an image. | 155 | [podman-image(1)](podman-image.1.md) | Manage images. | 156 | [podman-images(1)](podman-images.1.md) | List images in local storage. | 157 | [podman-import(1)](podman-import.1.md) | Import a tarball and save it as a filesystem image. | 158 | [podman-info(1)](podman-info.1.md) | Displays Podman related system information. | 159 | [podman-init(1)](podman-init.1.md) | Initialize a container | 160 | [podman-inspect(1)](podman-inspect.1.md) | Display a container or image's configuration. | 161 | [podman-kill(1)](podman-kill.1.md) | Kill the main process in one or more containers. | 162 | [podman-load(1)](podman-load.1.md) | Load an image from a container image archive into container storage. | 163 | [podman-logs(1)](podman-logs.1.md) | Display the logs of a container. | 164 | [podman-pause(1)](podman-pause.1.md) | Pause one or more containers. | 165 | [podman-pod(1)](podman-pod.1.md) | Management tool for groups of containers, called pods. | 166 | [podman-port(1)](podman-port.1.md) | List port mappings for a container. | 167 | [podman-ps(1)](podman-ps.1.md) | Prints out information about containers. | 168 | [podman-pull(1)](podman-pull.1.md) | Pull an image from a registry. | 169 | [podman-push(1)](podman-push.1.md) | Push an image from local storage to elsewhere. | 170 | [podman-restart(1)](podman-restart.1.md) | Restart one or more containers. | 171 | [podman-rm(1)](podman-rm.1.md) | Remove one or more containers. | 172 | [podman-rmi(1)](podman-rmi.1.md) | Removes one or more locally stored images. | 173 | [podman-run(1)](podman-run.1.md) | Run a command in a new container. | 174 | [podman-save(1)](podman-save.1.md) | Save an image to a container archive. | 175 | [podman-start(1)](podman-start.1.md) | Start one or more containers. | 176 | [podman-stop(1)](podman-stop.1.md) | Stop one or more running containers. | 177 | [podman-system(1)](podman-system.1.md) | Manage podman. | 178 | [podman-tag(1)](podman-tag.1.md) | Add an additional name to a local image. | 179 | [podman-top(1)](podman-top.1.md) | Display the running processes of a container. | 180 | [podman-unpause(1)](podman-unpause.1.md) | Unpause one or more containers. | 181 | [podman-version(1)](podman-version.1.md) | Display the Podman version information. | 182 | [podman-volume(1)](podman-volume.1.md) | Manage Volumes. | 183 ## FILES 184 185 **containers.conf** (`$HOME/.config/containers/containers.conf`) 186 187 Podman has builtin defaults for command line options. These defaults can be overridden using the containers.conf configuration files. 188 189 Users can modify defaults by creating the `$HOME/.config/containers/containers.conf` file. Podman merges its builtin defaults with the specified fields from this file, if it exists. Fields specified in the users file override the built-in defaults. 190 191 Podman uses builtin defaults if no containers.conf file is found. 192 193 ## SEE ALSO 194 **[podman(1)](podman.1.md)**, **[podman-system-service(1)](podman-system-service.1.md)**, **[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**