minio/Dockerfile.dev

FROM registry.access.redhat.com/ubi8/ubi-minimal:8.3

ARG TARGETARCH

LABEL maintainer="MinIO Inc <dev@min.io>"

COPY dockerscripts/docker-entrypoint.sh /usr/bin/
COPY minio /usr/bin/

ENV MINIO_UPDATE=off \
    MINIO_ROOT_USER_FILE=access_key \
    MINIO_ROOT_PASSWORD_FILE=secret_key \
    MINIO_KMS_SECRET_KEY_FILE=kms_master_key

RUN microdnf update --nodocs
RUN microdnf install curl ca-certificates shadow-utils util-linux --nodocs
RUN microdnf clean all && \
    chmod +x /usr/bin/minio  && \
    chmod +x /usr/bin/docker-entrypoint.sh

EXPOSE 9000

ENTRYPOINT ["/usr/bin/docker-entrypoint.sh"]

VOLUME ["/data"]

CMD ["minio"]
Remove alpine based image in favour or RedHat UBI (#11006) 2020-12-08 14:14:06 -05:00			`FROM registry.access.redhat.com/ubi8/ubi-minimal:8.3`

			`ARG TARGETARCH`
Move Dockerfile to go 1.9.1 (#5047) Additionally add Dockerfile.dev to build local development images. 2017-10-10 17:17:16 -04:00
Replace Minio refs in docs with MinIO and links (#7494) 2019-04-09 14:39:42 -04:00			`LABEL maintainer="MinIO Inc <dev@min.io>"`
Move Dockerfile to go 1.9.1 (#5047) Additionally add Dockerfile.dev to build local development images. 2017-10-10 17:17:16 -04:00
Remove healthcheck script for Docker image (#8095) There are multiple possibilities for running MinIO within a container e.g. configurable address, non-root user etc. This makes it difficult to identify actual IP / Port to use to check healthcheck status from within a container. It is simpler to use external healthcheck mechanisms like healthcheck command in docker-compose to check for MinIO health status. This is similar to how checks work in Kubernetes as well. This PR removes the healthcheck script used inside Docker container and ad documentation on how to use docker-compose based healthcheck mechanism. 2019-08-17 15:44:04 -04:00			`COPY dockerscripts/docker-entrypoint.sh /usr/bin/`
Quickly build dev docker images using 'make docker' (#6505) This PR simplifies the process of developer build of local docker containers using `make docker`. You need to provide a TAG i.e ``` TAG=y4m4/minio:exp make docker ``` 2018-09-25 13:33:25 -04:00			`COPY minio /usr/bin/`

Remove alpine based image in favour or RedHat UBI (#11006) 2020-12-08 14:14:06 -05:00			`ENV MINIO_UPDATE=off \`
feat: migrate to ROOT_USER/PASSWORD from ACCESS/SECRET_KEY (#11185) 2021-01-05 13:22:57 -05:00			`MINIO_ROOT_USER_FILE=access_key \`
			`MINIO_ROOT_PASSWORD_FILE=secret_key \`
kms: encrypt IAM/config data with the KMS (#12041) This commit changes the config/IAM encryption process. Instead of encrypting config data (users, policies etc.) with the root credentials MinIO now encrypts this data with a KMS - if configured. Therefore, this PR moves the MinIO-KMS configuration (via env. variables) to a "top-level" configuration. The KMS configuration cannot be stored in the config file since it is used to decrypt the config file in the first place. As a consequence, this commit also removes support for Hashicorp Vault - which has been deprecated anyway. Signed-off-by: Andreas Auernhammer <aead@mail.de> 2021-04-22 11:45:30 -04:00			`MINIO_KMS_SECRET_KEY_FILE=kms_master_key`
Move Dockerfile to go 1.9.1 (#5047) Additionally add Dockerfile.dev to build local development images. 2017-10-10 17:17:16 -04:00
fix: for containers use root-disk detection cleverly (#11593) root-disk implemented currently had issues where root disk partitions getting modified might race and provide incorrect results, to avoid this lets rely again back on DeviceID and match it instead. In-case of containers `/data` is one such extra entity that needs to be verified for root disk, due to how 'overlay' filesystem works and the 'overlay' presents a completely different 'device' id - using `/data` as another entity for fallback helps because our containers describe 'VOLUME' parameter that allows containers to automatically have a virtual `/data` that points to the container root path this can either be at `/` or `/var/lib/` (on different partition) 2021-02-22 13:32:21 -05:00			`RUN microdnf update --nodocs`
			`RUN microdnf install curl ca-certificates shadow-utils util-linux --nodocs`
			`RUN microdnf clean all && \`
Remove alpine based image in favour or RedHat UBI (#11006) 2020-12-08 14:14:06 -05:00			`chmod +x /usr/bin/minio && \`
			`chmod +x /usr/bin/docker-entrypoint.sh`
Move Dockerfile to go 1.9.1 (#5047) Additionally add Dockerfile.dev to build local development images. 2017-10-10 17:17:16 -04:00
			`EXPOSE 9000`

			`ENTRYPOINT ["/usr/bin/docker-entrypoint.sh"]`

Update volume in Dockerfiles (#5646) All sample commands in Minio docs use the volume path as /data. Updated the dockerfiles to follow the same pattern. Fixes #5635 2018-03-13 21:29:27 -04:00			`VOLUME ["/data"]`
Move Dockerfile to go 1.9.1 (#5047) Additionally add Dockerfile.dev to build local development images. 2017-10-10 17:17:16 -04:00
			`CMD ["minio"]`