diff --git a/README.md b/README.md index f53d97c30..a76b91c44 100644 --- a/README.md +++ b/README.md @@ -5,12 +5,11 @@ MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. It is API compatible with Amazon S3 cloud storage service. Use MinIO to build high performance infrastructure for machine learning, analytics and application data workloads. -This README provides quickstart instructions on running MinIO on baremetal hardware, including Docker-based installations. For Kubernetes environments, -use the [MinIO Kubernetes Operator](https://github.com/minio/operator/blob/master/README.md). +This README provides quickstart instructions on running MinIO on baremetal hardware, including container-based installations. For Kubernetes environments, use the [MinIO Kubernetes Operator](https://github.com/minio/operator/blob/master/README.md). -# Docker Installation +# Container Installation -Use the following commands to run a standalone MinIO server on a Docker container. +Use the following commands to run a standalone MinIO server as a container. Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, @@ -19,10 +18,10 @@ for more complete documentation. ## Stable -Run the following command to run the latest stable image of MinIO on a Docker container using an ephemeral data volume: +Run the following command to run the latest stable image of MinIO as a container using an ephemeral data volume: ```sh -docker run -p 9000:9000 minio/minio server /data +podman run -p 9000:9000 minio/minio server /data ``` The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded @@ -33,38 +32,13 @@ You can also connect using any S3-compatible tool, such as the MinIO Client `mc` [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. - -> NOTE: To deploy MinIO on Docker with persistent storage, you must map local persistent directories from the host OS to the container using the - `docker -v` option. For example, `-v /mnt/data:/data` maps the host OS drive at `/mnt/data` to `/data` on the Docker container. - -## Edge - -Run the following command to run the bleeding-edge image of MinIO on a Docker container using an ephemeral data volume: - -``` -docker run -p 9000:9000 minio/minio:edge server /data -``` - -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. - -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. - - -> NOTE: To deploy MinIO on Docker with persistent storage, you must map local persistent directories from the host OS to the container using the - `docker -v` option. For example, `-v /mnt/data:/data` maps the host OS drive at `/mnt/data` to `/data` on the Docker container. +> NOTE: To deploy MinIO on with persistent storage, you must map local persistent directories from the host OS to the container using the `podman -v` option. For example, `-v /mnt/data:/data` maps the host OS drive at `/mnt/data` to `/data` on the container. # macOS Use the following commands to run a standalone MinIO server on macOS. -Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication -require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, -with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) -for more complete documentation. +Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) for more complete documentation. ## Homebrew (recommended) @@ -82,13 +56,9 @@ brew uninstall minio brew install minio/stable/minio ``` -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. +The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. ## Binary Download @@ -100,14 +70,9 @@ chmod +x minio ./minio server /data ``` -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. - -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. +The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. # GNU/Linux @@ -130,19 +95,11 @@ The following table lists supported architectures. Replace the `wget` URL with t | 64-bit PowerPC LE (ppc64le) | https://dl.min.io/server/minio/release/linux-ppc64le/minio | | IBM Z-Series (S390X) | https://dl.min.io/server/minio/release/linux-s390x/minio | -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. +The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. - -> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication -require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, -with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) -for more complete documentation. +> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) for more complete documentation. # Microsoft Windows @@ -158,29 +115,11 @@ Use the following command to run a standalone MinIO server on the Windows host. minio.exe server D:\ ``` -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. +The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. -> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication -require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, -with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) -for more complete documentation. - -# FreeBSD - -MinIO does not provide an official FreeBSD binary. However, FreeBSD maintains an [upstream release](https://www.freshports.org/www/minio) using [pkg](https://github.com/freebsd/pkg): - -```sh -pkg install minio -sysrc minio_enable=yes -sysrc minio_disks=/home/user/Photos -service minio start -``` +> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) for more complete documentation. # Install from Source @@ -190,19 +129,11 @@ Use the following commands to compile and run a standalone MinIO server from sou GO111MODULE=on go install github.com/minio/minio@latest ``` -The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded -web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the -root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. +The MinIO deployment starts using default root credentials `minioadmin:minioadmin`. You can test the deployment using the MinIO Console, an embedded web-based object browser built into MinIO Server. Point a web browser running on the host machine to http://127.0.0.1:9000 and log in with the root credentials. You can use the Browser to create buckets, upload objects, and browse the contents of the MinIO server. -You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See -[Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, -see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. +You can also connect using any S3-compatible tool, such as the MinIO Client `mc` commandline tool. See [Test using MinIO Client `mc`](#test-using-minio-client-mc) for more information on using the `mc` commandline tool. For application developers, see https://docs.min.io/docs/ and click **MinIO SDKs** in the navigation to view MinIO SDKs for supported languages. - -> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication -require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, -with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) -for more complete documentation. +> NOTE: Standalone MinIO servers are best suited for early development and evaluation. Certain features such as versioning, object locking, and bucket replication require distributed deploying MinIO with Erasure Coding. For extended development and production, deploy MinIO with Erasure Coding enabled - specifically, with a *minimum* of 4 drives per MinIO server. See [MinIO Erasure Code Quickstart Guide](https://docs.min.io/docs/minio-erasure-code-quickstart-guide.html) for more complete documentation. MinIO strongly recommends *against* using compiled-from-source MinIO servers for production environments. @@ -273,6 +204,8 @@ The above statement is also valid for all gateway backends. ## Test using MinIO Console MinIO Server comes with an embedded web based object browser. Point your web browser to http://127.0.0.1:9000 to ensure your server has started successfully. +> NOTE: MinIO runs console on random port by default if you wish choose a specific port use `--console-address` to pick a specific interface and port. + | Dashboard | Creating a bucket | | ------------- | ------------- | | ![Dashboard](https://github.com/minio/minio/blob/master/docs/screenshots/pic1.png?raw=true) | ![Dashboard](https://github.com/minio/minio/blob/master/docs/screenshots/pic2.png?raw=true) | diff --git a/cmd/update.go b/cmd/update.go index ae8c27ac8..354bfd738 100644 --- a/cmd/update.go +++ b/cmd/update.go @@ -466,7 +466,7 @@ func getDownloadURL(releaseTag string) (downloadURL string) { // Check if we are docker environment, return docker update command if IsDocker() { // Construct release tag name. - return fmt.Sprintf("docker pull minio/minio:%s", releaseTag) + return fmt.Sprintf("podman pull minio/minio:%s", releaseTag) } // For binary only installations, we return link to the latest binary. diff --git a/cmd/update_test.go b/cmd/update_test.go index f08c740e9..a4f1e5e2d 100644 --- a/cmd/update_test.go +++ b/cmd/update_test.go @@ -92,8 +92,8 @@ func TestDownloadURL(t *testing.T) { minioVersion1 := releaseTimeToReleaseTag(UTCNow()) durl := getDownloadURL(minioVersion1) if IsDocker() { - if durl != "docker pull minio/minio:"+minioVersion1 { - t.Errorf("Expected %s, got %s", "docker pull minio/minio:"+minioVersion1, durl) + if durl != "podman pull minio/minio:"+minioVersion1 { + t.Errorf("Expected %s, got %s", "podman pull minio/minio:"+minioVersion1, durl) } } else { if runtime.GOOS == "windows" { diff --git a/docs/bucket/notifications/README.md b/docs/bucket/notifications/README.md index b16358933..7a16aa9ab 100644 --- a/docs/bucket/notifications/README.md +++ b/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 diff --git a/docs/disk-caching/DESIGN.md b/docs/disk-caching/DESIGN.md index 0113e9ba8..e57964b8a 100644 --- a/docs/disk-caching/DESIGN.md +++ b/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 diff --git a/docs/erasure/README.md b/docs/erasure/README.md index 86aad8731..404bfb9b2 100644 --- a/docs/erasure/README.md +++ b/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 \ diff --git a/docs/gateway/azure.md b/docs/gateway/azure.md index 7824d18c3..ec1201f0c 100644 --- a/docs/gateway/azure.md +++ b/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 diff --git a/docs/gateway/gcs.md b/docs/gateway/gcs.md index c76aeb956..54e6549a0 100644 --- a/docs/gateway/gcs.md +++ b/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" \ diff --git a/docs/gateway/hdfs.md b/docs/gateway/hdfs.md index df610a15d..824b5d938 100644 --- a/docs/gateway/hdfs.md +++ b/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" \ diff --git a/docs/gateway/nas.md b/docs/gateway/nas.md index 4a51d29d5..4cf89f038 100644 --- a/docs/gateway/nas.md +++ b/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 \ diff --git a/docs/gateway/s3.md b/docs/gateway/s3.md index 0778e9cc6..7b17a81dd 100644 --- a/docs/gateway/s3.md +++ b/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 diff --git a/docs/sts/etcd.md b/docs/sts/etcd.md index c4836979f..e164c5c8f 100644 --- a/docs/sts/etcd.md +++ b/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 \ diff --git a/main_contrib_test.go b/main_contrib_test.go index 43dfb647b..f8707c7bf 100644 --- a/main_contrib_test.go +++ b/main_contrib_test.go @@ -40,7 +40,7 @@ import ( // // 2. Run System-Tests (when using GitBash prefix this line with MSYS_NO_PATHCONV=1) // Note the the SERVER_ENDPOINT must be reachable from inside the docker container (so don't use localhost!) -// $ docker run -e MINT_MODE=full -e SERVER_ENDPOINT=192.168.47.11:9000 -e ACCESS_KEY=minioadmin -e SECRET_KEY=minioadmin -v /tmp/mint/log:/mint/log minio/mint +// $ podman run -e MINT_MODE=full -e SERVER_ENDPOINT=192.168.47.11:9000 -e ACCESS_KEY=minioadmin -e SECRET_KEY=minioadmin -v /tmp/mint/log:/mint/log minio/mint // // 3. Stop system under test by sending SIGTERM // $ ctrl+c