summaryrefslogtreecommitdiff
path: root/transfer.md
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2017-12-20 05:35:51 -0500
committerAtomic Bot <atomic-devel@projectatomic.io>2017-12-20 18:40:38 +0000
commit6065f18da6fa847ee67ff1e86e0a04ccb90dc587 (patch)
tree6b04ac560f4cc89e62ed77b21dfc27ac18326a47 /transfer.md
parent1f49f555af0709ea7c12becdb750ba60a00eaf1d (diff)
downloadpodman-6065f18da6fa847ee67ff1e86e0a04ccb90dc587.tar.gz
podman-6065f18da6fa847ee67ff1e86e0a04ccb90dc587.tar.bz2
podman-6065f18da6fa847ee67ff1e86e0a04ccb90dc587.zip
Cleanup Documentation and bash completions
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> Closes: #159 Approved by: TomSweeneyRedHat
Diffstat (limited to 'transfer.md')
-rw-r--r--transfer.md52
1 files changed, 28 insertions, 24 deletions
diff --git a/transfer.md b/transfer.md
index b72f0a584..1a2820cf3 100644
--- a/transfer.md
+++ b/transfer.md
@@ -23,29 +23,31 @@ For many troubleshooting and information collection steps, there may be an exist
Following provides equivalent with PODMAN tools for gathering information or jumping into containers, for operational use.
| Existing Step | PODMAN (and friends) |
-| :---: | :---: |
+| :--- | :--- |
+| `docker run` | [`podman run`](./docs/podman-run.1.md) |
| `docker exec` | [`podman exec`](./docs/podman-exec.1.md) |
| `docker info` | [`podman info`](./docs/podman-info.1.md) |
| `docker inspect` | [`podman inspect`](./docs/podman-inspect.1.md) |
| `docker logs` | [`podman logs`](./docs/podman-logs.1.md) |
-| `docker ps` | [`podman ps`](./docs/podman-ps.1.md) |
-| `docker stats` | [`podman stats`](./docs/podman-stats.1.md)|
+| `docker ps` | [`podman ps`](./docs/podman-ps.1.md) |
+| `docker stats`| [`podman stats`](./docs/podman-stats.1.md)|
## Development Transfer
There are other equivalents for these tools
| Existing Step | PODMAN (and friends) |
-| :---: | :---: |
-| `docker attach` | [`podman exec`](./docs/podman-attach.1.md) ***|
+| :--- | :--- |
+| `docker attach` | [`podman exec`](./docs/podman-attach.1.md)|
| `docker build` | [`buildah bud`](https://github.com/projectatomic/buildah/blob/master/docs/buildah-bud.md) |
-| `docker commit` | [`buildah commit`](https://github.com/projectatomic/buildah/blob/master/docs/buildah-commit.md) |
+| `docker commit` | [`podman commit`](./docs/podman-commit.1.md)|
| `docker cp` | [`podman mount`](./docs/podman-cp.1.md) **** |
| `docker create` | [`podman create`](./docs/podman-create.1.md) |
| `docker diff` | [`podman diff`](./docs/podman-diff.1.md) |
| `docker export` | [`podman export`](./docs/podman-export.1.md) |
| `docker history`| [`podman history`](./docs/podman-history.1.md)|
| `docker images` | [`podman images`](./docs/podman-images.1.md) |
+| `docker import` | [`podman import`](./docs/podman-import.1.md) |
| `docker kill` | [`podman kill`](./docs/podman-kill.1.md) |
| `docker load` | [`podman load`](./docs/podman-load.1.md) |
| `docker login` | [`podman login`](./docs/podman-login.1.md) |
@@ -58,36 +60,38 @@ There are other equivalents for these tools
| `docker rmi` | [`podman rmi`](./docs/podman-rmi.1.md) |
| `docker run` | [`podman run`](./docs/podman-run.1.md) |
| `docker save` | [`podman save`](./docs/podman-save.1.md) |
+| `docker start` | [`podman start`](./docs/podman-start.1.md) |
| `docker stop` | [`podman stop`](./docs/podman-stop.1.md) |
| `docker tag` | [`podman tag`](./docs/podman-tag.1.md) |
+| `docker top` | [`podman top`](./docs/podman-top.1.md) |
| `docker unpause`| [`podman unpause`](./docs/podman-unpause.1.md)|
| `docker version`| [`podman version`](./docs/podman-version.1.md)|
| `docker wait` | [`podman wait`](./docs/podman-wait.1.md) |
-*** Use `podman exec` to enter a container and `podman logs` to view the output of pid 1 of a container.
**** Use mount to take advantage of the entire linux tool chain rather then just cp. Read [`here`](./docs/podman-cp.1.md) for more information.
## Missing commands in podman
Those Docker commands currently do not have equivalents in `podman`:
- * `docker container`
- * `docker events`
- * `docker image`
- * `docker network`
- * `docker node`
- * `docker plugin`
- * `docker port`
- * `docker rename`
- * `docker restart`
- * `docker search`
- * `docker secret`
- * `docker service`
- * `docker stack`
- * `docker swarm`
- * `docker system`
- * `docker top`
- * `docker volume`
+| Missing command | Description|
+| :--- | :--- |
+| `docker container`||
+| `docker events` ||
+| `docker image` ||
+| `docker network` ||
+| `docker node` ||
+| `docker plugin` |podman does not support plugins. We recommend you use alternative OCI Runtimes or OCI Runtime Hooks to alter behaviour of podman.|
+| `docker port` ||
+| `docker rename` | podman does not support rename, you need to use `podman rm` and `podman create` to rename a container.|
+| `docker restart` | podman does not support restart. We recommend that you put your podman containers into a systemd unit file and use it for restarting applications.|
+| `docker search` ||
+| `docker secret` ||
+| `docker service` ||
+| `docker stack` ||
+| `docker swarm` | podman does not support swarm. We support Kubernetes for orchestration using [CRI-O](https://github.com/kubernetes-incubator/cri-o).|
+| `docker system` ||
+| `docker volume` | podman does not support volumes. Volumes should be built on the host operating system and then volume mounted into the containers.|
## Missing commands in Docker