fix: update README.md for new release (#12637)

rename all 'docker run' commands to 'podman run'

fixes #12633

docs/bucket/notifications/README.md

@@ -1298,7 +1298,7 @@ MINIO_NOTIFY_WEBHOOK_QUEUE_DIR    (path)      staging dir for undelivered messag
 MINIO_NOTIFY_WEBHOOK_QUEUE_LIMIT  (number)    maximum limit for undelivered messages, defaults to '100000'
 MINIO_NOTIFY_WEBHOOK_COMMENT      (sentence)  optionally add a comment to this setting
 MINIO_NOTIFY_WEBHOOK_CLIENT_CERT  (string)    client cert for Webhook mTLS auth
-MINIO_NOTIFY_WEBHOOK_CLIENT_KEY   (string)    client cert key for Webhook mTLS auth   
+MINIO_NOTIFY_WEBHOOK_CLIENT_KEY   (string)    client cert key for Webhook mTLS auth
 ```
 
 ```sh
@@ -1371,7 +1371,7 @@ Install an NSQ Daemon from [here](https://nsq.io/). Or use the following Docker
 command for starting an nsq daemon:
 
 ```
-docker run --rm -p 4150-4151:4150-4151 nsqio/nsq /nsqd
+podman run --rm -p 4150-4151:4150-4151 nsqio/nsq /nsqd
 ```
 
 ### Step 1: Add NSQ endpoint to MinIO

docs/disk-caching/DESIGN.md

@@ -39,16 +39,26 @@ Cache drives need to have `strictatime` or `relatime` enabled for disk caching f
 
 ```sh
 truncate -s 4G /tmp/data
+```
 
-mkfs.xfs /tmp/data     # build xfs filesystem on /tmp/data
+### Build xfs filesystem on /tmp/data
+```
+mkfs.xfs /tmp/data
+```
 
-sudo mkdir /mnt/cache  # create mount dir
+### Create mount dir
+```
+sudo mkdir /mnt/cache  #
+```
 
-sudo mount -o relatime /tmp/data /mnt/cache # mount xfs on /mnt/cache with atime.
+### Mount xfs on /mnt/cache with atime.
+```
+sudo mount -o relatime /tmp/data /mnt/cache
+```
 
-docker pull minio/minio
-
-docker run --net=host -e MINIO_ROOT_USER={s3-access-key} -e MINIO_ROOT_PASSWORD={s3-secret-key} \
+### Start using the cached drive with S3 gateway
+```
+podman run --net=host -e MINIO_ROOT_USER={s3-access-key} -e MINIO_ROOT_PASSWORD={s3-secret-key} \
     -e MINIO_CACHE_DRIVES=/cache -e MINIO_CACHE_QUOTA=99 -e MINIO_CACHE_AFTER=0 \
     -e MINIO_CACHE_WATERMARK_LOW=90 -e MINIO_CACHE_WATERMARK_HIGH=95 \
     -v /mnt/cache:/cache  minio/minio:latest gateway s3

docs/erasure/README.md

@@ -47,7 +47,7 @@ minio server /data{1...12}
 Example: Start MinIO server in a 8 drives setup, using MinIO Docker image. 
 
 ```sh
-docker run -p 9000:9000 --name minio \
+podman run -p 9000:9000 --name minio \
   -v /mnt/data1:/data1 \
   -v /mnt/data2:/data2 \
   -v /mnt/data3:/data3 \

docs/gateway/azure.md

@@ -4,7 +4,7 @@ MinIO Gateway adds Amazon S3 compatibility to Microsoft Azure Blob Storage.
 ## Run MinIO Gateway for Microsoft Azure Blob Storage
 ### Using Docker
 ```
-docker run -p 9000:9000 --name azure-s3 \
+podman run -p 9000:9000 --name azure-s3 \
  -e "MINIO_ROOT_USER=azurestorageaccountname" \
  -e "MINIO_ROOT_PASSWORD=azurestorageaccountkey" \
  minio/minio gateway azure

docs/gateway/gcs.md

@@ -21,7 +21,7 @@ MinIO GCS Gateway allows you to access Google Cloud Storage (GCS) with Amazon S3
 
 ### 1.2 Run MinIO GCS Gateway Using Docker
 ```sh
-docker run -p 9000:9000 --name gcs-s3 \
+podman run -p 9000:9000 --name gcs-s3 \
  -v /path/to/credentials.json:/credentials.json \
  -e "GOOGLE_APPLICATION_CREDENTIALS=/credentials.json" \
  -e "MINIO_ROOT_USER=minioaccountname" \

docs/gateway/hdfs.md

@@ -23,7 +23,7 @@ minio gateway hdfs hdfs://namenode:8200
 ### Using Docker
 Using docker is experimental, most Hadoop environments are not dockerized and may require additional steps in getting this to work properly. You are better off just using the binary in this situation.
 ```
-docker run -p 9000:9000 \
+podman run -p 9000:9000 \
  --name hdfs-s3 \
  -e "MINIO_ROOT_USER=minio" \
  -e "MINIO_ROOT_PASSWORD=minio123" \

docs/gateway/nas.md

@@ -9,7 +9,7 @@ MinIO Gateway adds Amazon S3 compatibility to NAS storage. You may run multiple
 Please ensure to replace `/shared/nasvol` with actual mount path.
 
 ```
-docker run -p 9000:9000 --name nas-s3 \
+podman run -p 9000:9000 --name nas-s3 \
  -e "MINIO_ROOT_USER=minio" \
  -e "MINIO_ROOT_PASSWORD=minio123" \
  -v /shared/nasvol:/container/vol \

docs/gateway/s3.md

@@ -7,7 +7,7 @@ As a prerequisite to run MinIO S3 gateway, you need valid AWS S3 access key and
 
 ### Using Docker
 ```
-docker run -p 9000:9000 --name minio-s3 \
+podman run -p 9000:9000 --name minio-s3 \
  -e "MINIO_ROOT_USER=aws_s3_access_key" \
  -e "MINIO_ROOT_PASSWORD=aws_s3_secret_key" \
  minio/minio gateway s3
@@ -46,15 +46,17 @@ Minimum permissions required if you wish to provide restricted access with your
             "Sid": "readonly",
             "Effect": "Allow",
             "Action": [
-                "s3:GetObject",
-                "s3:ListBucket"
+                "s3:GetObject"
             ],
-            "Resource": "arn:aws:s3:::testbucket"
+            "Resource": "arn:aws:s3:::testbucket/*"
         },
         {
             "Sid": "readonly",
             "Effect": "Allow",
-            "Action": "s3:HeadBucket",
+            "Action": [
+                "s3:HeadBucket",
+                "s3:ListBucket"
+            ],
             "Resource": "arn:aws:s3:::testbucket"
         }
     ]
@@ -94,7 +96,7 @@ minio gateway s3
 
 ### Using Docker
 ```
-docker run -p 9000:9000 --name minio-s3 \
+podman run -p 9000:9000 --name minio-s3 \
  -e "MINIO_ROOT_USER=access_key" \
  -e "MINIO_ROOT_PASSWORD=secret_key" \
  minio/minio gateway s3 https://s3_compatible_service_endpoint:port

docs/sts/etcd.md

@@ -11,7 +11,7 @@ etcd uses [gcr.io/etcd-development/etcd](https://console.cloud.google.com/gcr/im
 ```
 rm -rf /tmp/etcd-data.tmp && mkdir -p /tmp/etcd-data.tmp && \
   docker rmi gcr.io/etcd-development/etcd:v3.3.9 || true && \
-  docker run \
+  podman run \
   -p 2379:2379 \
   -p 2380:2380 \
   --mount type=bind,source=/tmp/etcd-data.tmp,destination=/etcd-data \