18ec933085
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)
31 lines
760 B
Docker
31 lines
760 B
Docker
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_ACCESS_KEY_FILE=access_key \
|
|
MINIO_SECRET_KEY_FILE=secret_key \
|
|
MINIO_ROOT_USER_FILE=access_key \
|
|
MINIO_ROOT_PASSWORD_FILE=secret_key \
|
|
MINIO_KMS_MASTER_KEY_FILE=kms_master_key \
|
|
MINIO_SSE_MASTER_KEY_FILE=sse_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"]
|