MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2024-12-24 06:05:55 -05:00
Code Issues Packages Projects Releases Wiki Activity
55dd017e62
minio/Dockerfile.release

40 lines
1.0 KiB
Docker
Raw Normal View History

Fix docker files to enable GO111MODULE
2019-04-04 13:13:33 -04:00
FROM golang:1.12-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 && \
Fix docker files to enable GO111MODULE
2019-04-04 13:13:33 -04:00
git clone https://github.com/minio/minio && cd minio/dockerscripts && \
Deprecate auto detection of container user (#7930) There is no reliable way to handle fallbacks for MinIO deployments, due to various command line options and multiple locations which require access inside container. Parsing command line options is tricky to figure out which is the backend disk etc, we did try to fix this in implementations of check-user.go but it wasn't complete and introduced more bugs. This PR simplifies the entire approach to rather than running Docker container as non-root by default always, it allows users to opt-in. Such that they are aware that that is what they are planning to do. In-fact there are other ways docker containers can be run as regular users, without modifying our internal behavior and adding more complexities.
2019-07-17 14:20:55 -04:00
go build -tags kqueue -ldflags "-s -w" -o /usr/bin/healthcheck healthcheck.go
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 --from=0 /usr/bin/healthcheck /usr/bin/healthcheck
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 \
MINIO_SECRET_KEY_FILE=secret_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 && \
chmod +x /usr/bin/docker-entrypoint.sh && \
Deprecate auto detection of container user (#7930) There is no reliable way to handle fallbacks for MinIO deployments, due to various command line options and multiple locations which require access inside container. Parsing command line options is tricky to figure out which is the backend disk etc, we did try to fix this in implementations of check-user.go but it wasn't complete and introduced more bugs. This PR simplifies the entire approach to rather than running Docker container as non-root by default always, it allows users to opt-in. Such that they are aware that that is what they are planning to do. In-fact there are other ways docker containers can be run as regular users, without modifying our internal behavior and adding more complexities.
2019-07-17 14:20:55 -04:00
chmod +x /usr/bin/healthcheck
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
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
HEALTHCHECK --interval=1m CMD healthcheck
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
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"]
Reference in New Issue Copy Permalink