mirror of
https://github.com/minio/minio.git
synced 2024-12-24 22:25:54 -05:00
e5fb6294a7
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.
26 lines
622 B
Docker
26 lines
622 B
Docker
FROM alpine:3.9
|
|
|
|
LABEL maintainer="MinIO Inc <dev@min.io>"
|
|
|
|
COPY dockerscripts/docker-entrypoint.sh /usr/bin/
|
|
COPY minio /usr/bin/
|
|
|
|
ENV MINIO_UPDATE off
|
|
ENV MINIO_ACCESS_KEY_FILE=access_key \
|
|
MINIO_SECRET_KEY_FILE=secret_key \
|
|
MINIO_SSE_MASTER_KEY_FILE=sse_master_key
|
|
|
|
RUN \
|
|
apk add --no-cache ca-certificates 'curl>7.61.0' 'su-exec>=0.2' && \
|
|
echo 'hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4' >> /etc/nsswitch.conf && \
|
|
chmod +x /usr/bin/minio && \
|
|
chmod +x /usr/bin/docker-entrypoint.sh
|
|
|
|
EXPOSE 9000
|
|
|
|
ENTRYPOINT ["/usr/bin/docker-entrypoint.sh"]
|
|
|
|
VOLUME ["/data"]
|
|
|
|
CMD ["minio"]
|