oyd
/
minio
6
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6299 Commits
1 Branch
0 Tags
89 MiB
Tag: Branch: Tree: 3f20011862
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3f20011862'
${ noResults }
minio/Dockerfile.release

36 lines
856 B
Raw Normal View History Unescape

Migrate to go1.13 to avail all new features (#8203) Read more https://blog.golang.org/go1.13
5 years ago
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
6 years ago
ENV GOPATH /go
ENV CGO_ENABLED 0
Fix docker files to enable GO111MODULE
6 years ago
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
6 years ago
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.
5 years ago
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
6 years ago
Add crypto context errors (#8740) Currently when connections to vault fail, client perpetually retries this leads to assumptions that the server has issues and masks the problem. Re-purpose *crypto.Error* type to send appropriate errors back to the client.
5 years ago
FROM alpine:3.10
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.
8 years ago
Replace Minio refs in docs with MinIO and links (#7494)
6 years ago
LABEL maintainer="MinIO Inc <dev@min.io>"
change MAINTAINER to LABEL (#5843)
7 years ago
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
6 years ago
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.
8 years ago
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
7 years ago
ENV MINIO_UPDATE off
Add custom secret names for Docker (#5355)
7 years ago
ENV MINIO_ACCESS_KEY_FILE=access_key \
Add KMS master key from Docker secret (#7825)
6 years ago
MINIO_SECRET_KEY_FILE=secret_key \
Migrate config to KV data format (#8392) - adding oauth support to MinIO browser (#8400) by @kanagaraj - supports multi-line get/set/del for all config fields - add support for comments, allow toggle - add extensive validation of config before saving - support MinIO browser to support proper claims, using STS tokens - env support for all config parameters, legacy envs are also supported with all documentation now pointing to latest ENVs - preserve accessKey/secretKey from FS mode setups - add history support implements three APIs - ClearHistory - RestoreHistory - ListHistory - add help command support for each config parameters - all the bug fixes after migration to KV, and other bug fixes encountered during testing.
5 years ago
MINIO_KMS_MASTER_KEY_FILE=kms_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
7 years ago
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.
8 years ago
RUN \
Add support for customizable user (#7569)
6 years ago
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.
8 years ago
echo 'hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4' >> /etc/nsswitch.conf && \
Replace Minio refs in docs with MinIO and links (#7494)
6 years ago
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
8 years ago
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.
5 years ago
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.
8 years ago
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
7 years ago
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.
8 years ago
CMD ["minio"]