4.3 KiB
Select the tab for either Podman or Docker to see instructions for pulling the MinIO container image. The instructions include examples for both quay.io and DockerHub:
Podman
- quay.io
-
podman pull quay.io/minio/minio - DockerHub
-
podman pull docker://minio/minio
Docker
- quay.io
-
docker pull quay.io/minio/minio - DockerHub
-
docker pull docker://minio/minio
Podman
Run the following command to retrieve logs from the container.
Replace the container name with the value specified to
--name in the previous step.
podman logs minioThe command should return output similar to the following:
Docker
Run the following command to retrieve logs from the container.
Replace the container name with the value specified to
--name in the previous step.
docker logs minioThe command should return output similar to the following:
MinIO Web Console
You can access the MinIO Web Console by entering http://localhost:9090 in your preferred browser. Any traffic to the MinIO Console port on the local host redirects to the container.
Log in with the MINIO_ROOT_USER and MINIO_ROOT_PASSWORD configured in the environment
file specified to the container.
You can use the MinIO Console for general administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration. Each MinIO server includes its own embedded MinIO Console.
If your local host firewall permits external access to the Console port, other hosts on the same network can access the Console using the IP or hostname for your local host.
MinIO CLI (mc)
You can access the MinIO deployment over a Terminal or Shell using
the MinIO Client <minio-client> (mc). See MinIO Client Installation Quickstart <mc-install>
for instructions on installing mc.
Create a new alias <mc alias set> corresponding to the MinIO
deployment. Use a hostname or IP address for your local machine along
with the S3 API port 9000 to access the MinIO deployment.
Any traffic to that port on the local host redirects to the
container.
mc alias set http://localhost:9000 myminioadmin minio-secret-key-change-meReplace myminioadmin and
minio-secret-key-change-me with the MINIO_ROOT_USER and MINIO_ROOT_PASSWORD values
in the environment file specified to the container.
The command should return success if the container is running and accessible at the specified port.
You can then interact with the container using any mc command. If your local host
firewall permits external access to the MinIO S3 API port, other hosts
on the same network can access the MinIO deployment using the IP or
hostname for your local host.
This procedure assumes you have a working Podman installation configured to run in "Rootfull" mode.
"Rootless" modes may not provide sufficient permissions to run KES
with the necessary security settings. See the relevant "rootless" documentation <blob/main/docs/tutorials/rootless_tutorial.md>
for more information.