MyFavMirrors
/
minio
mirror of https://github.com/minio/minio.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
minio/Dockerfile.release

36 lines
855 B
Docker
Raw Normal View History

Migrate to go1.13 to avail all new features (#8203) Read more https://blog.golang.org/go1.13
2019-09-08 19:44:15 -04:00
FROM golang:1.13-alpine
Implement Docker healthcheck script in Go (#7105) Go script makes it easy to read/maintain. Also updated the timeout in Dockerfiles from 5s to default 30s and test interval to 1m Higher timeout makes sense as server may sometimes respond slowly if under high load as reported in #6974 Fixes #6974
2019-02-20 11:12:03 -05:00
ENV GOPATH /go
ENV CGO_ENABLED 0
Fix docker files to enable GO111MODULE
2019-04-04 13:13:33 -04:00
ENV GO111MODULE on
Implement Docker healthcheck script in Go (#7105) Go script makes it easy to read/maintain. Also updated the timeout in Dockerfiles from 5s to default 30s and test interval to 1m Higher timeout makes sense as server may sometimes respond slowly if under high load as reported in #6974 Fixes #6974
2019-02-20 11:12:03 -05:00
RUN \
apk add --no-cache git && \
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
git clone https://github.com/minio/minio
Implement Docker healthcheck script in Go (#7105) Go script makes it easy to read/maintain. Also updated the timeout in Dockerfiles from 5s to default 30s and test interval to 1m Higher timeout makes sense as server may sometimes respond slowly if under high load as reported in #6974 Fixes #6974
2019-02-20 11:12:03 -05:00
Fix docker files to enable GO111MODULE
2019-04-04 13:13:33 -04:00
FROM alpine:3.9
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -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>"
change MAINTAINER to LABEL (#5843)
2018-04-24 12:57:48 -04:00
Implement Docker healthcheck script in Go (#7105) Go script makes it easy to read/maintain. Also updated the timeout in Dockerfiles from 5s to default 30s and test interval to 1m Higher timeout makes sense as server may sometimes respond slowly if under high load as reported in #6974 Fixes #6974
2019-02-20 11:12:03 -05:00
COPY dockerscripts/docker-entrypoint.sh /usr/bin/
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -04:00
Support in-place upgrades of new minio binary and releases. (#4961) This PR allows 'minio update' to not only shows update banner but also allows for in-place upgrades. Updates are done safely by validating the downloaded sha256 of the binary. Fixes #4781
2017-12-15 15:33:42 -05:00
ENV MINIO_UPDATE off
Add custom secret names for Docker (#5355)
2018-01-09 00:16:25 -05:00
ENV MINIO_ACCESS_KEY_FILE=access_key \
Add KMS master key from Docker secret (#7825)
2019-07-17 15:55:26 -04:00
MINIO_SECRET_KEY_FILE=secret_key \
MINIO_SSE_MASTER_KEY_FILE=sse_master_key
Support in-place upgrades of new minio binary and releases. (#4961) This PR allows 'minio update' to not only shows update banner but also allows for in-place upgrades. Updates are done safely by validating the downloaded sha256 of the binary. Fixes #4781
2017-12-15 15:33:42 -05:00
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -04:00
RUN \
Add support for customizable user (#7569)
2019-06-10 10:57:42 -04:00
apk add --no-cache ca-certificates 'curl>7.61.0' 'su-exec>=0.2' && \
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -04:00
echo 'hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4' >> /etc/nsswitch.conf && \
Replace Minio refs in docs with MinIO and links (#7494)
2019-04-09 14:39:42 -04:00
curl https://dl.min.io/server/minio/release/linux-amd64/minio > /usr/bin/minio && \
Added HEALTHCHECK in release Dockerfiles (#4550) A new script `healthcheck.sh` checks for http status 200/404
2017-06-20 22:24:45 -04:00
chmod +x /usr/bin/minio && \
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
chmod +x /usr/bin/docker-entrypoint.sh
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -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"]
Add docker release files. (#4473) We used to release by building directly on the docker hub auto build process, which is sufficient for edge but it is not a good idea to do it for stable releases. Do not build docker release binaries again, but instead use the released binaries themselves which are signed and validated.
2017-06-14 05:08:35 -04:00
CMD ["minio"]