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.
4612 Commits
1 Branch
0 Tags
89 MiB
Tag: Branch: Tree: 7c72d14027
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7c72d14027'
${ noResults }
minio/Dockerfile.release

29 lines
741 B
Raw Normal View History Unescape

Move all Dockerfiles to alpine-3.6 (#4797) Refer #4759. Fix this to avoid issues like below ``` docker run --rm minio/minio:edge-armhf version minio: <ERROR> .... is not compiled by Go >= 1.8.3. ... recompile... ```
7 years ago
FROM alpine:3.6
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
MAINTAINER Minio Inc <dev@minio.io>
Added HEALTHCHECK in release Dockerfiles (#4550) A new script `healthcheck.sh` checks for http status 200/404
8 years ago
Fix healthcheck issue with Docker containers (#5011) Fixes #5010
7 years ago
COPY dockerscripts/docker-entrypoint.sh dockerscripts/healthcheck.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 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 \
apk add --no-cache ca-certificates && \
apk add --no-cache --virtual .build-deps curl && \
echo 'hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4' >> /etc/nsswitch.conf && \
curl https://dl.minio.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 && \
chmod +x /usr/bin/docker-entrypoint.sh && \
chmod +x /usr/bin/healthcheck.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"]
VOLUME ["/export"]
Added HEALTHCHECK in release Dockerfiles (#4550) A new script `healthcheck.sh` checks for http status 200/404
8 years ago
HEALTHCHECK --interval=30s --timeout=5s \
CMD /usr/bin/healthcheck.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
CMD ["minio"]