podman migration and fixes

Author: dmarrazzo

documentation/modules/ROOT/pages/skopeo.adoc

@@ -163,11 +163,27 @@ Let's copy a container from a remote registry to a local registry (the one runni
 
 Having a Docker Host running in local machine, run the following command:
 
+[tabs]
+====
+Docker::
++
+--
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
 skopeo copy docker://quay.io/rhdevelopers/quarkus-demo:v1 docker-daemon:docker.io/rhdevelopers/quarkus-demo:skopeo
 ----
+--
+Podman::
++
+--
+[.console-input]
+[source,bash,subs="+macros,+attributes"]
+----
+skopeo copy docker://quay.io/rhdevelopers/quarkus-demo:v1 containers-storage:rhdevelopers/quarkus-demo:skopeo
+----
+--
+====
 
 [.console-output]
 [source,bash,subs="+macros,+attributes"]
@@ -189,7 +205,7 @@ If you run the `podman images` command, you'll see the image downloaded with the
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
-docker images
+podman images
 ----
 
 [.console-output]
@@ -208,9 +224,11 @@ Run the following command in a terminal window:
 [.console-input]
 [source,bash,subs="+macros,+attributes"]
 ----
-podman run --rm -ti -p 5000:5000 --restart=always --name registry registry:2
+podman run --rm -ti -p 5000:5000 --name registry registry:2
 ----
 
+TIP: If your port 5000 is already in use, you can run the registry in a different port e.g. `-p 5001:5000` .
+
 In a new terminal window, run the `copy` command setting origin to quay.io and the destination, the registry created in the previous step:
 
 [.console-input]
@@ -244,7 +262,7 @@ time="2023-04-12T13:29:37.927391556Z" level=info msg="response completed" go.ver
 172.17.0.1 - - [12/Apr/2023:13:29:37 +0000] "PUT /v2/rhdevelopers/quarkus-demo/manifests/skopeo HTTP/1.1" 201 0 "" "skopeo/1.11.1"
 ----
 
-Shut down the container registry by stopping the `docker run` process.
+Shut down the container registry by stopping the `podman run` process.
 
 == Deleting a Container