docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove deprecated images

This commit is contained in:
Tianon Gravi 2021-10-08 16:39:01 -07:00
parent ce4a817c4a
commit 30237fdec8
107 changed files with 0 additions and 2664 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
adoptopenjdk/README-short.txt
View File

@ -1 +0,0 @@
Official Images for OpenJDK + HotSpot and OpenJDK + Eclipse OpenJ9 binaries built by AdoptOpenJDK.

318
adoptopenjdk/README.md
View File

@ -1,318 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "adoptopenjdk/README.md"
IT IS AUTO-GENERATED
(from the other files in "adoptopenjdk/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is officially deprecated in favor of [the `eclipse-temurin` image](https://hub.docker.com/_/eclipse-temurin/), and will receive no further updates after 2021-08-01 (Aug 01, 2021). Please adjust your usage accordingly.
# Quick reference
- **Maintained by**:
[AdoptOpenJDK](https://github.com/AdoptOpenJDK/openjdk-docker)
- **Where to get help**:
[AdoptOpenJDK Slack](https://adoptopenjdk.net/slack.html); [AdoptOpenJDK Mailing List](https://mail.openjdk.java.net/mailman/listinfo/adoption-discuss); [Eclipse OpenJ9 Slack](https://www.eclipse.org/openj9/oj9_joinslack.html); [Eclipse OpenJ9 Mailing List](https://dev.eclipse.org/mailman/listinfo/openj9-dev)
# Supported tags and respective `Dockerfile` links
(See ["What's the difference between 'Shared' and 'Simple' tags?" in the FAQ](https://github.com/docker-library/faq#whats-the-difference-between-shared-and-simple-tags).)
## Simple Tags
- [`8u292-b10-jdk-hotspot-focal`, `8-jdk-hotspot-focal`, `8-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-hotspot-windowsservercore-1809`, `8-jdk-hotspot-windowsservercore-1809`, `8-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-hotspot-windowsservercore-ltsc2016`, `8-jdk-hotspot-windowsservercore-ltsc2016`, `8-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-focal`, `8-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-windowsservercore-1809`, `8-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-windowsservercore-ltsc2016`, `8-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-focal`, `11-jdk-hotspot-focal`, `11-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-windowsservercore-1809`, `11-jdk-hotspot-windowsservercore-1809`, `11-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-windowsservercore-ltsc2016`, `11-jdk-hotspot-windowsservercore-ltsc2016`, `11-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-focal`, `11-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-windowsservercore-1809`, `11-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-windowsservercore-ltsc2016`, `11-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-focal`, `15-jdk-hotspot-focal`, `15-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-windowsservercore-1809`, `15-jdk-hotspot-windowsservercore-1809`, `15-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-windowsservercore-ltsc2016`, `15-jdk-hotspot-windowsservercore-ltsc2016`, `15-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-focal`, `15-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-windowsservercore-1809`, `15-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-windowsservercore-ltsc2016`, `15-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-focal`, `16-jdk-hotspot-focal`, `16-hotspot-focal`, `hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-windowsservercore-1809`, `16-jdk-hotspot-windowsservercore-1809`, `16-hotspot-windowsservercore-1809`, `hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-windowsservercore-ltsc2016`, `16-jdk-hotspot-windowsservercore-ltsc2016`, `16-hotspot-windowsservercore-ltsc2016`, `hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-focal`, `16-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-windowsservercore-1809`, `16-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-windowsservercore-ltsc2016`, `16-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-focal`, `8-jdk-openj9-focal`, `8-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-1809`, `8-jdk-openj9-windowsservercore-1809`, `8-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-ltsc2016`, `8-jdk-openj9-windowsservercore-ltsc2016`, `8-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-focal`, `8-jre-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-1809`, `8-jre-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-ltsc2016`, `8-jre-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-focal`, `11-jdk-openj9-focal`, `11-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-1809`, `11-jdk-openj9-windowsservercore-1809`, `11-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`, `11-jdk-openj9-windowsservercore-ltsc2016`, `11-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-focal`, `11-jre-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-1809`, `11-jre-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`, `11-jre-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-focal`, `15-jdk-openj9-focal`, `15-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-1809`, `15-jdk-openj9-windowsservercore-1809`, `15-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-ltsc2016`, `15-jdk-openj9-windowsservercore-ltsc2016`, `15-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-focal`, `15-jre-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-1809`, `15-jre-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-ltsc2016`, `15-jre-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-focal`, `16-jdk-openj9-focal`, `16-openj9-focal`, `openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-1809`, `16-jdk-openj9-windowsservercore-1809`, `16-openj9-windowsservercore-1809`, `openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`, `16-jdk-openj9-windowsservercore-ltsc2016`, `16-openj9-windowsservercore-ltsc2016`, `openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-focal`, `16-jre-openj9-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-1809`, `16-jre-openj9-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`, `16-jre-openj9-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
## Shared Tags
- `8u292-b10-jdk-hotspot`, `8-jdk-hotspot`, `8-hotspot`, `8-jdk`, `8`:
- [`8u292-b10-jdk-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `8u292-b10-jdk-hotspot-windowsservercore`, `8-jdk-hotspot-windowsservercore`, `8-hotspot-windowsservercore`:
- [`8u292-b10-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `8u292-b10-jre-hotspot`, `8-jre-hotspot`, `8-jre`:
- [`8u292-b10-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `8u292-b10-jre-hotspot-windowsservercore`, `8-jre-hotspot-windowsservercore`:
- [`8u292-b10-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`8u292-b10-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `11.0.11_9-jdk-hotspot`, `11-jdk-hotspot`, `11-hotspot`, `11-jdk`, `11`:
- [`11.0.11_9-jdk-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `11.0.11_9-jdk-hotspot-windowsservercore`, `11-jdk-hotspot-windowsservercore`, `11-hotspot-windowsservercore`:
- [`11.0.11_9-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `11.0.11_9-jre-hotspot`, `11-jre-hotspot`, `11-jre`:
- [`11.0.11_9-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `11.0.11_9-jre-hotspot-windowsservercore`, `11-jre-hotspot-windowsservercore`:
- [`11.0.11_9-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`11.0.11_9-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `15.0.2_7-jdk-hotspot`, `15-jdk-hotspot`, `15-hotspot`, `15-jdk`, `15`:
- [`15.0.2_7-jdk-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `15.0.2_7-jdk-hotspot-windowsservercore`, `15-jdk-hotspot-windowsservercore`, `15-hotspot-windowsservercore`:
- [`15.0.2_7-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `15.0.2_7-jre-hotspot`, `15-jre-hotspot`, `15-jre`:
- [`15.0.2_7-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `15.0.2_7-jre-hotspot-windowsservercore`, `15-jre-hotspot-windowsservercore`:
- [`15.0.2_7-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`15.0.2_7-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `16.0.1_9-jdk-hotspot`, `16-jdk-hotspot`, `16-hotspot`, `hotspot`, `16-jdk`, `16`, `jdk`, `latest`:
- [`16.0.1_9-jdk-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/ubuntu/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `16.0.1_9-jdk-hotspot-windowsservercore`, `16-jdk-hotspot-windowsservercore`, `16-hotspot-windowsservercore`, `hotspot-windowsservercore`:
- [`16.0.1_9-jdk-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jdk-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `16.0.1_9-jre-hotspot`, `16-jre-hotspot`, `16-jre`:
- [`16.0.1_9-jre-hotspot-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/ubuntu/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `16.0.1_9-jre-hotspot-windowsservercore`, `16-jre-hotspot-windowsservercore`:
- [`16.0.1_9-jre-hotspot-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.hotspot.releases.full)
- [`16.0.1_9-jre-hotspot-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.hotspot.releases.full)
- `8u292-b10-jdk-openj9-0.26.0`, `8-jdk-openj9`, `8-openj9`:
- [`8u292-b10-jdk-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `8u292-b10-jdk-openj9-0.26.0-windowsservercore`, `8-jdk-openj9-windowsservercore`, `8-openj9-windowsservercore`:
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `8u292-b10-jre-openj9-0.26.0`, `8-jre-openj9`:
- [`8u292-b10-jre-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `8u292-b10-jre-openj9-0.26.0-windowsservercore`, `8-jre-openj9-windowsservercore`:
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`8u292-b10-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/8/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `11.0.11_9-jdk-openj9-0.26.0`, `11-jdk-openj9`, `11-openj9`:
- [`11.0.11_9-jdk-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `11.0.11_9-jdk-openj9-0.26.0-windowsservercore`, `11-jdk-openj9-windowsservercore`, `11-openj9-windowsservercore`:
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `11.0.11_9-jre-openj9-0.26.0`, `11-jre-openj9`:
- [`11.0.11_9-jre-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `11.0.11_9-jre-openj9-0.26.0-windowsservercore`, `11-jre-openj9-windowsservercore`:
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`11.0.11_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/11/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `15.0.2_7-jdk-openj9-0.24.0`, `15-jdk-openj9`, `15-openj9`:
- [`15.0.2_7-jdk-openj9-0.24.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `15.0.2_7-jdk-openj9-0.24.0-windowsservercore`, `15-jdk-openj9-windowsservercore`, `15-openj9-windowsservercore`:
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jdk-openj9-0.24.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `15.0.2_7-jre-openj9-0.24.0`, `15-jre-openj9`:
- [`15.0.2_7-jre-openj9-0.24.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `15.0.2_7-jre-openj9-0.24.0-windowsservercore`, `15-jre-openj9-windowsservercore`:
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`15.0.2_7-jre-openj9-0.24.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/15/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `16.0.1_9-jdk-openj9-0.26.0`, `16-jdk-openj9`, `16-openj9`, `openj9`:
- [`16.0.1_9-jdk-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/ubuntu/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `16.0.1_9-jdk-openj9-0.26.0-windowsservercore`, `16-jdk-openj9-windowsservercore`, `16-openj9-windowsservercore`, `openj9-windowsservercore`:
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jdk-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jdk/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `16.0.1_9-jre-openj9-0.26.0`, `16-jre-openj9`:
- [`16.0.1_9-jre-openj9-0.26.0-focal`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/ubuntu/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
- `16.0.1_9-jre-openj9-0.26.0-windowsservercore`, `16-jre-openj9-windowsservercore`:
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-1809`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-1809/Dockerfile.openj9.releases.full)
- [`16.0.1_9-jre-openj9-0.26.0-windowsservercore-ltsc2016`](https://github.com/AdoptOpenJDK/openjdk-docker/blob/c945a5b588b63553a7bb36c28b6751716e35070c/16/jre/windows/windowsservercore-ltsc2016/Dockerfile.openj9.releases.full)
# Quick reference (cont.)
- **Where to file issues**:
[GitHub](https://github.com/AdoptOpenJDK/openjdk-docker/issues); The [adoptopenjdk support](https://adoptopenjdk.net/support.html) page has more information on quality, roadmap and support levels for AdoptOpenJDK builds;
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/adoptopenjdk/), [`arm32v7`](https://hub.docker.com/r/arm32v7/adoptopenjdk/), [`arm64v8`](https://hub.docker.com/r/arm64v8/adoptopenjdk/), [`ppc64le`](https://hub.docker.com/r/ppc64le/adoptopenjdk/), [`s390x`](https://hub.docker.com/r/s390x/adoptopenjdk/), [`windows-amd64`](https://hub.docker.com/r/winamd64/adoptopenjdk/)
- **Published image artifact details**:
[repo-info repo's `repos/adoptopenjdk/` directory](https://github.com/docker-library/repo-info/blob/master/repos/adoptopenjdk) ([history](https://github.com/docker-library/repo-info/commits/master/repos/adoptopenjdk))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/adoptopenjdk` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fadoptopenjdk)
[official-images repo's `library/adoptopenjdk` file](https://github.com/docker-library/official-images/blob/master/library/adoptopenjdk) ([history](https://github.com/docker-library/official-images/commits/master/library/adoptopenjdk))
- **Source of this description**:
[docs repo's `adoptopenjdk/` directory](https://github.com/docker-library/docs/tree/master/adoptopenjdk) ([history](https://github.com/docker-library/docs/commits/master/adoptopenjdk))
## Overview
The images in this repository contain OpenJDK binaries that are built by AdoptOpenJDK and contain both HotSpot and Eclipse OpenJ9 JVMs.
# What is AdoptOpenJDK ?
[AdoptOpenJDK](https://adoptopenjdk.net/) is a community of Java™ user group members, Java developers and vendors who are advocates of OpenJDK, the open source project which forms the basis of the Java programming language and platform. AdoptOpenJDK provides prebuilt OpenJDK binaries from a fully open source set of build scripts and infrastructure. AdoptOpenJDK builds and tests binaries for different source code streams based upon OpenJDK. Our binaries undergo extensive testing, and the Releases have passed all the available OpenJDK test suites and our additional tests (donated by the community), ensuring the best quality binary available.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
![logo](https://raw.githubusercontent.com/docker-library/docs/0db0af87e256d941bf011e3b5b06ca4a8edb6b84/adoptopenjdk/logo.png)
# What is Eclipse OpenJ9 ?
[Eclipse OpenJ9](https://www.eclipse.org/openj9/) is a high performance, scalable, Java virtual machine (JVM) implementation that has a proven track record of running Java applications in production environments. Contributed to the Eclipse project by IBM, the OpenJ9 JVM underpins the IBM SDK, Java Technology Edition product that is a core component of many IBM Enterprise software products. Continued development of OpenJ9 at the Eclipse foundation ensures wider collaboration, fresh innovation, and the opportunity to influence the development of OpenJ9 for the next generation of Java applications. OpenJDK binaries that include Eclipse OpenJ9 are available through AdoptOpenJDK.
# Images
There are two types of Docker images here: the Java Development Kit (JDK) and the Java Runtime Environment (JRE). These images can be used as the basis for custom built images for running your applications.
### Multi-Arch Image
Docker Images for the following architectures are now available:
- HotSpot
- `amd64`, `arm32v7`, `arm64v8`, `ppc64le`, `s390x`, `windows-amd64`
- Eclipse OpenJ9
- `amd64`, `ppc64le`, `s390x`, `windows-amd64`
# How to use this Image
To run a pre-built jar file with the latest OpenJDK 11 with HotSpot JRE image, use the following Dockerfile:
```dockerfile
FROM adoptopenjdk:11-jre-hotspot
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
To do the same with the latest OpenJDK 11 with Eclipse OpenJ9 JRE image, use the following Dockerfile:
```dockerfile
FROM adoptopenjdk:11-jre-openj9
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
You can build and run the Docker Image as shown in the following example:
```console
docker build -t japp .
docker run -it --rm japp
```
If you want to place the jar file on the host file system instead of inside the container, you can mount the host path onto the container by using the following commands:
```dockerfile
FROM adoptopenjdk:12.0.1_12-jdk-openj9-0.14.1
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
```console
docker build -t japp .
docker run -it -v /path/on/host/system/jars:/opt/app japp
```
# Image Variants
The `adoptopenjdk` images come in many flavors, each designed for a specific use case.
## `adoptopenjdk:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
Some of these tags may have names like focal in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu.
## `adoptopenjdk:<version>-windowsservercore`
This image is based on [Windows Server Core (`microsoft/windowsservercore`)](https://hub.docker.com/r/microsoft/windowsservercore/). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.
For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft:
- [Windows Server Quick Start](https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_server)
- [Windows 10 Quick Start](https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_10)
# License
The Dockerfiles and associated scripts are licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
Licenses for the products installed within the images:
- Eclipse OpenJ9 + OpenJDK: The combined works license is [GNU GPL v2 with Classpath Exception](http://openjdk.java.net/legal/gplv2+ce.html).
- OpenJDK: The project license is GNU GPL v2 with Classpath Exception.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `adoptopenjdk/` directory](https://github.com/docker-library/repo-info/tree/master/repos/adoptopenjdk).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

67
adoptopenjdk/content.md
View File

@ -1,67 +0,0 @@
## Overview
The images in this repository contain OpenJDK binaries that are built by AdoptOpenJDK and contain both HotSpot and Eclipse OpenJ9 JVMs.
# What is AdoptOpenJDK ?
[AdoptOpenJDK](https://adoptopenjdk.net/) is a community of Java™ user group members, Java developers and vendors who are advocates of OpenJDK, the open source project which forms the basis of the Java programming language and platform. AdoptOpenJDK provides prebuilt OpenJDK binaries from a fully open source set of build scripts and infrastructure. AdoptOpenJDK builds and tests binaries for different source code streams based upon OpenJDK. Our binaries undergo extensive testing, and the Releases have passed all the available OpenJDK test suites and our additional tests (donated by the community), ensuring the best quality binary available.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
%%LOGO%%
# What is Eclipse OpenJ9 ?
[Eclipse OpenJ9](https://www.eclipse.org/openj9/) is a high performance, scalable, Java virtual machine (JVM) implementation that has a proven track record of running Java applications in production environments. Contributed to the Eclipse project by IBM, the OpenJ9 JVM underpins the IBM SDK, Java Technology Edition product that is a core component of many IBM Enterprise software products. Continued development of OpenJ9 at the Eclipse foundation ensures wider collaboration, fresh innovation, and the opportunity to influence the development of OpenJ9 for the next generation of Java applications. OpenJDK binaries that include Eclipse OpenJ9 are available through AdoptOpenJDK.
# Images
There are two types of Docker images here: the Java Development Kit (JDK) and the Java Runtime Environment (JRE). These images can be used as the basis for custom built images for running your applications.
### Multi-Arch Image
Docker Images for the following architectures are now available:
- HotSpot
- `amd64`, `arm32v7`, `arm64v8`, `ppc64le`, `s390x`, `windows-amd64`
- Eclipse OpenJ9
- `amd64`, `ppc64le`, `s390x`, `windows-amd64`
# How to use this Image
To run a pre-built jar file with the latest OpenJDK 11 with HotSpot JRE image, use the following Dockerfile:
```dockerfile
FROM %%IMAGE%%:11-jre-hotspot
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
To do the same with the latest OpenJDK 11 with Eclipse OpenJ9 JRE image, use the following Dockerfile:
```dockerfile
FROM %%IMAGE%%:11-jre-openj9
RUN mkdir /opt/app
COPY japp.jar /opt/app
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
You can build and run the Docker Image as shown in the following example:
```console
docker build -t japp .
docker run -it --rm japp
```
If you want to place the jar file on the host file system instead of inside the container, you can mount the host path onto the container by using the following commands:
```dockerfile
FROM %%IMAGE%%:12.0.1_12-jdk-openj9-0.14.1
CMD ["java", "-jar", "/opt/app/japp.jar"]
```
```console
docker build -t japp .
docker run -it -v /path/on/host/system/jars:/opt/app japp
```

1
adoptopenjdk/deprecated.md
View File

@ -1 +0,0 @@
This image is officially deprecated in favor of [the `eclipse-temurin` image](https://hub.docker.com/_/eclipse-temurin/), and will receive no further updates after 2021-08-01 (Aug 01, 2021). Please adjust your usage accordingly.

1
adoptopenjdk/get-help.md
View File

@ -1 +0,0 @@
[AdoptOpenJDK Slack](https://adoptopenjdk.net/slack.html); [AdoptOpenJDK Mailing List](https://mail.openjdk.java.net/mailman/listinfo/adoption-discuss); [Eclipse OpenJ9 Slack](https://www.eclipse.org/openj9/oj9_joinslack.html); [Eclipse OpenJ9 Mailing List](https://dev.eclipse.org/mailman/listinfo/openj9-dev)

1
adoptopenjdk/github-repo
View File

@ -1 +0,0 @@
https://github.com/AdoptOpenJDK/openjdk-docker

1
adoptopenjdk/issues.md
View File

@ -1 +0,0 @@
[GitHub](%%GITHUB-REPO%%/issues); The [adoptopenjdk support](https://adoptopenjdk.net/support.html) page has more information on quality, roadmap and support levels for AdoptOpenJDK builds;

6
adoptopenjdk/license.md
View File

@ -1,6 +0,0 @@
The Dockerfiles and associated scripts are licensed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
Licenses for the products installed within the images:
- Eclipse OpenJ9 + OpenJDK: The combined works license is [GNU GPL v2 with Classpath Exception](http://openjdk.java.net/legal/gplv2+ce.html).
- OpenJDK: The project license is GNU GPL v2 with Classpath Exception.

BIN
adoptopenjdk/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 10 KiB

1
adoptopenjdk/maintainer.md
View File

@ -1 +0,0 @@
[AdoptOpenJDK](%%GITHUB-REPO%%)

1
crux/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

78
crux/README.md
View File

@ -1,78 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "crux/README.md"
IT IS AUTO-GENERATED
(from the other files in "crux/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to maintainer inactivity (last updated Nov 2018; [docker-library/official-images#5073](https://github.com/docker-library/official-images/pull/5073)).
See [docker-library/official-images#7130](https://github.com/docker-library/official-images/pull/7130) for discussion around an in-progress upstream update.
# Quick reference
- **Maintained by**:
[Docker Crux](https://github.com/cruxlinux/docker-crux)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
**No supported tags**
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/therealprologic/docker-crux/issues](https://github.com/therealprologic/docker-crux/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
**No supported architectures**
- **Published image artifact details**:
[repo-info repo's `repos/crux/` directory](https://github.com/docker-library/repo-info/blob/master/repos/crux) ([history](https://github.com/docker-library/repo-info/commits/master/repos/crux))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/crux` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fcrux)
[official-images repo's `library/crux` file](https://github.com/docker-library/official-images/blob/master/library/crux) ([history](https://github.com/docker-library/official-images/commits/master/library/crux))
- **Source of this description**:
[docs repo's `crux/` directory](https://github.com/docker-library/docs/tree/master/crux) ([history](https://github.com/docker-library/docs/commits/master/crux))
# What is CRUX?
CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is "keep it simple", which it reflects in a simple tar.gz-based package system, BSD-style initscripts, and a relatively small collection of trimmed packages. The secondary focus is utilization of new Linux features and recent tools and libraries. CRUX also has a ports system which makes it easy to install and upgrade applications.
# Why use CRUX?
There are many Linux distributions out there these days, so what makes CRUX any better than the others? The choice of distribution is a matter of taste, really. Here are a few hints about the tastes and goals of the people behind CRUX. CRUX is made with simplicity in mind from beginning to end.
Making it easy to create new and update old packages is essential; updating a package in CRUX is often just a matter of typing `pkgmk -d -u`. The usage of ports helps keep your packages up-to-date; not the latest bleeding-edge-alpha version, but the latest stable version. Other features include creating packages optimized for your processor, eg. by compiling with `-march=x86-64`, and avoiding cluttering the filesystem with files you'll never use, eg. `/usr/doc/*`, etc. If you need more information about a specific program, other than information found in the man-page, Google usually knows all about it.
Finally, it strives to use new features as they become available, as long as they are consistent with the rest of the goals. In short, CRUX might suit you very well if you are:
- A somewhat experienced Linux user who wants a clean and solid Linux distribution as the foundation of your installation.
- A person who prefers editing configuration files with an editor to using a GUI.
- Someone who does not hesitate to download and compile programs from the source.
# License
View [license information](https://crux.nu/Main/Handbook3-3-Intro) for the software contained in this image (scroll to the "License" section at the end of the linked document).
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `crux/` directory](https://github.com/docker-library/repo-info/tree/master/repos/crux).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

15
crux/content.md
View File

@ -1,15 +0,0 @@
# What is CRUX?
CRUX is a lightweight Linux distribution for the x86-64 architecture targeted at experienced Linux users. The primary focus of this distribution is "keep it simple", which it reflects in a simple tar.gz-based package system, BSD-style initscripts, and a relatively small collection of trimmed packages. The secondary focus is utilization of new Linux features and recent tools and libraries. CRUX also has a ports system which makes it easy to install and upgrade applications.
# Why use CRUX?
There are many Linux distributions out there these days, so what makes CRUX any better than the others? The choice of distribution is a matter of taste, really. Here are a few hints about the tastes and goals of the people behind CRUX. CRUX is made with simplicity in mind from beginning to end.
Making it easy to create new and update old packages is essential; updating a package in CRUX is often just a matter of typing `pkgmk -d -u`. The usage of ports helps keep your packages up-to-date; not the latest bleeding-edge-alpha version, but the latest stable version. Other features include creating packages optimized for your processor, eg. by compiling with `-march=x86-64`, and avoiding cluttering the filesystem with files you'll never use, eg. `/usr/doc/*`, etc. If you need more information about a specific program, other than information found in the man-page, Google usually knows all about it.
Finally, it strives to use new features as they become available, as long as they are consistent with the rest of the goals. In short, CRUX might suit you very well if you are:
- A somewhat experienced Linux user who wants a clean and solid Linux distribution as the foundation of your installation.
- A person who prefers editing configuration files with an editor to using a GUI.
- Someone who does not hesitate to download and compile programs from the source.

3
crux/deprecated.md
View File

@ -1,3 +0,0 @@
This image is deprecated due to maintainer inactivity (last updated Nov 2018; [docker-library/official-images#5073](https://github.com/docker-library/official-images/pull/5073)).
See [docker-library/official-images#7130](https://github.com/docker-library/official-images/pull/7130) for discussion around an in-progress upstream update.

1
crux/github-repo
View File

@ -1 +0,0 @@
https://github.com/therealprologic/docker-crux

1
crux/license.md
View File

@ -1 +0,0 @@
View [license information](https://crux.nu/Main/Handbook3-3-Intro) for the software contained in this image (scroll to the "License" section at the end of the linked document).

BIN
crux/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 9.3 KiB

1
crux/maintainer.md
View File

@ -1 +0,0 @@
[Docker Crux](https://github.com/cruxlinux/docker-crux)

1
euleros/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

83
euleros/README.md
View File

@ -1,83 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "euleros/README.md"
IT IS AUTO-GENERATED
(from the other files in "euleros/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to inactivity (last updated Apr 2019; [docker-library/official-images#5644](https://github.com/docker-library/official-images/pull/5644)).
# Quick reference
- **Maintained by**:
[The EulerOS Project](https://github.com/euleros/euleros-docker-images)
- **Where to get help**:
[the EulerOS Community Forums](http://developer.huawei.com/ict/forum/forum.php?mod=forumdisplay&fid=400257&page=) or 8x5 Comprehensive Support 400 8828 000
# Supported tags and respective `Dockerfile` links
- [`2.3.1809`, `latest`](https://github.com/euleros/euleros-docker-images/blob/db22e2c392c3922d2c674110c90667576618f348/2.3.1809/x86_64/Dockerfile)
- [`2.3.1806`](https://github.com/euleros/euleros-docker-images/blob/e304245f74141e6e856a017c8d204c27300c1da8/2.3.1806/x86_64/Dockerfile)
- [`2.3.1803`](https://github.com/euleros/euleros-docker-images/blob/5afd15edcd49671adefb6dff87537f2943ae1107/2.3.1803/x86_64/Dockerfile)
- [`2.2`](https://github.com/euleros/euleros-docker-images/blob/959f378638f222bd1eebe8dccf267cccbc118174/2.2/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/euleros/euleros-docker-images/issues](https://github.com/euleros/euleros-docker-images/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/euleros/), [`arm64v8`](https://hub.docker.com/r/arm64v8/euleros/)
- **Published image artifact details**:
[repo-info repo's `repos/euleros/` directory](https://github.com/docker-library/repo-info/blob/master/repos/euleros) ([history](https://github.com/docker-library/repo-info/commits/master/repos/euleros))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/euleros` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Feuleros)
[official-images repo's `library/euleros` file](https://github.com/docker-library/official-images/blob/master/library/euleros) ([history](https://github.com/docker-library/official-images/commits/master/library/euleros))
- **Source of this description**:
[docs repo's `euleros/` directory](https://github.com/docker-library/docs/tree/master/euleros) ([history](https://github.com/docker-library/docs/commits/master/euleros))
![logo](https://raw.githubusercontent.com/docker-library/docs/67335f712632d352c94de4beeff0120d7c68168c/euleros/logo.png)
# EulerOS
EulerOS provides enhanced security, compatibility and easy-to-use features along with high reliability. It meets the increasing requirements of Linux OS in enterprise applications and provides a compelling choice of open IT platform for users. EulerOS integrates the advanced Linux technologies, delivers more value to enterprise users in terms of high capability, stability, usability and expansibility. And it helps you reallocate resources from maintaining the status quo to tackling new challenges.
## Operating System
Linux/Unix, Other V2.0
## High Lights
- Extreme Security: EulerOS is one of the most secure operating systems available, which provides variety of security technologies to prevent intrusions and protect your system.
- Carrier-class Reliability, Availability and Serviceability: EulerOS customers are able to provide carrier-class ultra-long-term reliability and stability to their users.
- High Performance: EulerOS has done a lot of optimization in the compilation, virtual memory, CPU scheduling, IO drive, network and file system and so on.
## Resources
[Administrators Guide](http://developer.huawei.com/ict/en/doc/site-euleros-administrators-guide-en/index.html/en-us)
# License
View [license information](https://github.com/euleros/euleros-docker-images/blob/master/LICENSE) for the software contained in this image and [EULA](http://developer.huawei.com/ict/en/site-euleros/article/privacy-policy) for the end user license agreement.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `euleros/` directory](https://github.com/docker-library/repo-info/tree/master/repos/euleros).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

19
euleros/content.md
View File

@ -1,19 +0,0 @@
%%LOGO%%
# EulerOS
EulerOS provides enhanced security, compatibility and easy-to-use features along with high reliability. It meets the increasing requirements of Linux OS in enterprise applications and provides a compelling choice of open IT platform for users. EulerOS integrates the advanced Linux technologies, delivers more value to enterprise users in terms of high capability, stability, usability and expansibility. And it helps you reallocate resources from maintaining the status quo to tackling new challenges.
## Operating System
Linux/Unix, Other V2.0
## High Lights
- Extreme Security: EulerOS is one of the most secure operating systems available, which provides variety of security technologies to prevent intrusions and protect your system.
- Carrier-class Reliability, Availability and Serviceability: EulerOS customers are able to provide carrier-class ultra-long-term reliability and stability to their users.
- High Performance: EulerOS has done a lot of optimization in the compilation, virtual memory, CPU scheduling, IO drive, network and file system and so on.
## Resources
[Administrators Guide](http://developer.huawei.com/ict/en/doc/site-euleros-administrators-guide-en/index.html/en-us)

1
euleros/deprecated.md
View File

@ -1 +0,0 @@
This image is deprecated due to inactivity (last updated Apr 2019; [docker-library/official-images#5644](https://github.com/docker-library/official-images/pull/5644)).

1
euleros/get-help.md
View File

@ -1 +0,0 @@
[the EulerOS Community Forums](http://developer.huawei.com/ict/forum/forum.php?mod=forumdisplay&fid=400257&page=) or 8x5 Comprehensive Support 400 8828 000

1
euleros/github-repo
View File

@ -1 +0,0 @@
https://github.com/euleros/euleros-docker-images

1
euleros/license.md
View File

@ -1 +0,0 @@
View [license information](https://github.com/euleros/euleros-docker-images/blob/master/LICENSE) for the software contained in this image and [EULA](http://developer.huawei.com/ict/en/site-euleros/article/privacy-policy) for the end user license agreement.

BIN
euleros/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 3.4 KiB

1
euleros/maintainer.md
View File

@ -1 +0,0 @@
[The EulerOS Project](%%GITHUB-REPO%%)

1
fsharp/README-short.txt
View File

@ -1 +0,0 @@
F# is a multi-paradigm language encompassing functional, imperative, and object-oriented styles

84
fsharp/README.md
View File

@ -1,84 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "fsharp/README.md"
IT IS AUTO-GENERATED
(from the other files in "fsharp/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
These images have been removed in favor of the [official .NET SDK image](https://hub.docker.com/_/microsoft-dotnet-sdk/), provided and maintained by Microsoft.
# Quick reference
- **Maintained by**:
[the F# Community](https://github.com/fsprojects/docker-fsharp)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`latest`, `10`, `10.10`, `10.10.0`](https://github.com/fsprojects/docker-fsharp/blob/a47a73b4b99d85720e191680e29f1bd1d62724ea/10.10.0/mono/Dockerfile)
- [`4`, `4.1`, `4.1.34`](https://github.com/fsprojects/docker-fsharp/blob/a47a73b4b99d85720e191680e29f1bd1d62724ea/4.1.34/mono/Dockerfile)
- [`netcore`, `10-netcore`, `10.10-netcore`, `10.10.0-netcore`](https://github.com/fsprojects/docker-fsharp/blob/a47a73b4b99d85720e191680e29f1bd1d62724ea/10.10.0/netcore/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/fsprojects/docker-fsharp/issues](https://github.com/fsprojects/docker-fsharp/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/fsharp/), [`arm64v8`](https://hub.docker.com/r/arm64v8/fsharp/)
- **Published image artifact details**:
[repo-info repo's `repos/fsharp/` directory](https://github.com/docker-library/repo-info/blob/master/repos/fsharp) ([history](https://github.com/docker-library/repo-info/commits/master/repos/fsharp))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/fsharp` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Ffsharp)
[official-images repo's `library/fsharp` file](https://github.com/docker-library/official-images/blob/master/library/fsharp) ([history](https://github.com/docker-library/official-images/commits/master/library/fsharp))
- **Source of this description**:
[docs repo's `fsharp/` directory](https://github.com/docker-library/docs/tree/master/fsharp) ([history](https://github.com/docker-library/docs/commits/master/fsharp))
# What is F#?
F# (pronounced F sharp) is a strongly typed, multi-paradigm programming language that encompasses functional, imperative, and object-oriented programming techniques. F# is most often used as a cross-platform CLI language, but can also be used to generate JavaScript and GPU code.
> [wikipedia.org/wiki/F Sharp (programming language)](https://en.wikipedia.org/wiki/F_Sharp_%28programming_language%29)
![logo](https://raw.githubusercontent.com/docker-library/docs/7d8c02340482b7f0c08c9fa7dc534d72314d3a22/fsharp/logo.png)
# How to use this image
## Start your application inside this image
The most straightforward way to use this image is to use it both as the build and runtime environment. In your `Dockerfile`, you can write something similar to the following:
```dockerfile
FROM fsharp
COPY . /app
RUN xbuild /app/myproject.sln
```
This will copy your application source code into the image and use `xbuild` to build it.
# License
View [the Apache 2.0 license](https://github.com/fsharp/fsharp/blob/d518f91418ef43a61875a5d932147b97fd0f47f3/LICENSE) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `fsharp/` directory](https://github.com/docker-library/repo-info/tree/master/repos/fsharp).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

21
fsharp/content.md
View File

@ -1,21 +0,0 @@
# What is F#?
F# (pronounced F sharp) is a strongly typed, multi-paradigm programming language that encompasses functional, imperative, and object-oriented programming techniques. F# is most often used as a cross-platform CLI language, but can also be used to generate JavaScript and GPU code.
> [wikipedia.org/wiki/F Sharp (programming language)](https://en.wikipedia.org/wiki/F_Sharp_%28programming_language%29)
%%LOGO%%
# How to use this image
## Start your application inside this image
The most straightforward way to use this image is to use it both as the build and runtime environment. In your `Dockerfile`, you can write something similar to the following:
```dockerfile
FROM %%IMAGE%%
COPY . /app
RUN xbuild /app/myproject.sln
```
This will copy your application source code into the image and use `xbuild` to build it.

1
fsharp/deprecated.md
View File

@ -1 +0,0 @@
These images have been removed in favor of the [official .NET SDK image](https://hub.docker.com/_/microsoft-dotnet-sdk/), provided and maintained by Microsoft.

1
fsharp/github-repo
View File

@ -1 +0,0 @@
https://github.com/fsprojects/docker-fsharp

1
fsharp/license.md
View File

@ -1 +0,0 @@
View [the Apache 2.0 license](https://github.com/fsharp/fsharp/blob/d518f91418ef43a61875a5d932147b97fd0f47f3/LICENSE) for the software contained in this image.

BIN
fsharp/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 8.3 KiB

1
fsharp/maintainer.md
View File

@ -1 +0,0 @@
[the F# Community](%%GITHUB-REPO%%)

1
kaazing-gateway/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

117
kaazing-gateway/README.md
View File

@ -1,117 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "kaazing-gateway/README.md"
IT IS AUTO-GENERATED
(from the other files in "kaazing-gateway/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to inactivity (last updated Jul 2018; [docker-library/official-images#4575](https://github.com/docker-library/official-images/pull/4575)).
# Quick reference
- **Maintained by**:
[the Kaazing Docker Maintainers](https://github.com/kaazing/gateway.docker)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`5.6.0`, `5.6`, `5`, `latest`](https://github.com/kaazing/gateway.docker/blob/a40c8da9d2c2925bdd78b9a6d1b6da3fe89322d1/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/kaazing/gateway.docker/issues](https://github.com/kaazing/gateway.docker/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/kaazing-gateway/), [`arm64v8`](https://hub.docker.com/r/arm64v8/kaazing-gateway/)
- **Published image artifact details**:
[repo-info repo's `repos/kaazing-gateway/` directory](https://github.com/docker-library/repo-info/blob/master/repos/kaazing-gateway) ([history](https://github.com/docker-library/repo-info/commits/master/repos/kaazing-gateway))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/kaazing-gateway` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fkaazing-gateway)
[official-images repo's `library/kaazing-gateway` file](https://github.com/docker-library/official-images/blob/master/library/kaazing-gateway) ([history](https://github.com/docker-library/official-images/commits/master/library/kaazing-gateway))
- **Source of this description**:
[docs repo's `kaazing-gateway/` directory](https://github.com/docker-library/docs/tree/master/kaazing-gateway) ([history](https://github.com/docker-library/docs/commits/master/kaazing-gateway))
# What is the KAAZING Gateway?
The Kaazing Gateway is a network gateway created to provide a single access point for real-time web based protocols that supports load balancing, clustering, and security management. It is designed to provide scalable and secure bidirectional event-based communication over the web; on every platform, browser, and device.
![logo](https://raw.githubusercontent.com/docker-library/docs/ba0031dd881f3b95d30ebf1d6094e99985d8eb6d/kaazing-gateway/logo.png)
# How to use this image
## Up and Running
By default the gateway runs a WebSocket echo service similar to [websocket.org](https://www.websocket.org/echo.html).
You must give your gateway container a hostname. To do this, use the `docker run -h somehostname` option, along with the -e option to define an environment variable, GATEWAY_OPTS, to pass this hostname to the gateway configuration (your hostname may vary):
```console
$ docker run --name some-kaazing-gateway -h somehostname -e GATEWAY_OPTS="-Dgateway.hostname=somehostname -Xmx512m -Djava.security.egd=file:/dev/urandom" -d -p 8000:8000 kaazing-gateway
```
Note: the additional GATEWAY_OPTS options, `-Xmx512m -Djava.security.egd=file:/dev/urandom`, are added in order to preserve these values from the original Dockerfile for the gateway. The `-Xmx512m` value specifies a minimum Java heap size of 512 MB, and `-Djava.security.egd=file:/dev/urandom` is to facilitate faster startup on VMs. See the `Dockerfile` link referenced above for details.
You should then be able to connect to ws://somehostname:8000 from the [WebSocket echo test](https://www.websocket.org/echo.html).
Note: all of the above assumes that `somehostname` is resolvable from your browser. You may need to add an etc/hosts entry for `somehostname` on your `dockerhost ip`.
## Custom Configuration
To launch a container with a specific configuration you can do the following:
```console
$ docker run --name some-kaazing-gateway -h somehostname -e GATEWAY_OPTS="-Dgateway.hostname=somehostname -Xmx512m -Djava.security.egd=file:/dev/urandom" -v /some/gateway-config.xml:/kaazing-gateway/conf/gateway-config.xml:ro -d kaazing-gateway
```
For information on the syntax of the Kaazing Gateway configuration files, see [the official documentation](https://kaazing.com/doc/5.0/index.html) (specifically the *For Administrators* section).
If you wish to adapt the default Gateway configuration file, you can use a command such as the following to copy the file from a running Kaazing Gateway container:
```console
$ docker cp some-kaazing:/kaazing-gateway/conf/gateway-config-minimal.xml /some/gateway-config.xml
```
As above, this can also be accomplished more cleanly using a simple `Dockerfile`:
```dockerfile
FROM kaazing-gateway
COPY gateway-config.xml conf/gateway-config.xml
```
Then, build with `docker build -t some-custom-kaazing-gateway .` and run:
```console
$ docker run --name some-kaazing-gateway -d some-custom-kaazing-gateway
```
## GATEWAY_OPTS
For more information on the GATEWAY_OPTS environment variable, see [Configure Kaazing Gateway Using the GATEWAY_OPTS Environment Variable](https://kaazing.com/doc/5.0/admin-reference/p_configure_gateway_opts/).
# License
View [license information](https://github.com/kaazing/gateway/blob/master/LICENSE.txt) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `kaazing-gateway/` directory](https://github.com/docker-library/repo-info/tree/master/repos/kaazing-gateway).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

56
kaazing-gateway/content.md
View File

@ -1,56 +0,0 @@
# What is the KAAZING Gateway?
The Kaazing Gateway is a network gateway created to provide a single access point for real-time web based protocols that supports load balancing, clustering, and security management. It is designed to provide scalable and secure bidirectional event-based communication over the web; on every platform, browser, and device.
%%LOGO%%
# How to use this image
## Up and Running
By default the gateway runs a WebSocket echo service similar to [websocket.org](https://www.websocket.org/echo.html).
You must give your gateway container a hostname. To do this, use the `docker run -h somehostname` option, along with the -e option to define an environment variable, GATEWAY_OPTS, to pass this hostname to the gateway configuration (your hostname may vary):
```console
$ docker run --name some-kaazing-gateway -h somehostname -e GATEWAY_OPTS="-Dgateway.hostname=somehostname -Xmx512m -Djava.security.egd=file:/dev/urandom" -d -p 8000:8000 %%IMAGE%%
```
Note: the additional GATEWAY_OPTS options, `-Xmx512m -Djava.security.egd=file:/dev/urandom`, are added in order to preserve these values from the original Dockerfile for the gateway. The `-Xmx512m` value specifies a minimum Java heap size of 512 MB, and `-Djava.security.egd=file:/dev/urandom` is to facilitate faster startup on VMs. See the `Dockerfile` link referenced above for details.
You should then be able to connect to ws://somehostname:8000 from the [WebSocket echo test](https://www.websocket.org/echo.html).
Note: all of the above assumes that `somehostname` is resolvable from your browser. You may need to add an etc/hosts entry for `somehostname` on your `dockerhost ip`.
## Custom Configuration
To launch a container with a specific configuration you can do the following:
```console
$ docker run --name some-kaazing-gateway -h somehostname -e GATEWAY_OPTS="-Dgateway.hostname=somehostname -Xmx512m -Djava.security.egd=file:/dev/urandom" -v /some/gateway-config.xml:/kaazing-gateway/conf/gateway-config.xml:ro -d %%IMAGE%%
```
For information on the syntax of the Kaazing Gateway configuration files, see [the official documentation](https://kaazing.com/doc/5.0/index.html) (specifically the *For Administrators* section).
If you wish to adapt the default Gateway configuration file, you can use a command such as the following to copy the file from a running Kaazing Gateway container:
```console
$ docker cp some-kaazing:/kaazing-gateway/conf/gateway-config-minimal.xml /some/gateway-config.xml
```
As above, this can also be accomplished more cleanly using a simple `Dockerfile`:
```dockerfile
FROM %%IMAGE%%
COPY gateway-config.xml conf/gateway-config.xml
```
Then, build with `docker build -t some-custom-kaazing-gateway .` and run:
```console
$ docker run --name some-kaazing-gateway -d some-custom-kaazing-gateway
```
## GATEWAY_OPTS
For more information on the GATEWAY_OPTS environment variable, see [Configure Kaazing Gateway Using the GATEWAY_OPTS Environment Variable](https://kaazing.com/doc/5.0/admin-reference/p_configure_gateway_opts/).

1
kaazing-gateway/deprecated.md
View File

@ -1 +0,0 @@
This image is deprecated due to inactivity (last updated Jul 2018; [docker-library/official-images#4575](https://github.com/docker-library/official-images/pull/4575)).

1
kaazing-gateway/github-repo
View File

@ -1 +0,0 @@
https://github.com/kaazing/gateway.docker

1
kaazing-gateway/license.md
View File

@ -1 +0,0 @@
View [license information](https://github.com/kaazing/gateway/blob/master/LICENSE.txt) for the software contained in this image.

BIN
kaazing-gateway/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 19 KiB

1
kaazing-gateway/maintainer.md
View File

@ -1 +0,0 @@
[the Kaazing Docker Maintainers](%%GITHUB-REPO%%)

1
known/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

111
known/README.md
View File

@ -1,111 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "known/README.md"
IT IS AUTO-GENERATED
(from the other files in "known/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to inactivity (last updated Aug 2018; [docker-library/official-images#4670](https://github.com/docker-library/official-images/pull/4670)).
# Quick reference
- **Maintained by**:
[Known](https://github.com/idno/Known-Docker)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`0.9.9`, `0.9`, `0`, `latest`](https://github.com/idno/Known-Docker/blob/3454a52b4ad48e22b95e706dba9ff953cf84c2b1/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/idno/Known-Docker/issues](https://github.com/idno/Known-Docker/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/known/), [`arm64v8`](https://hub.docker.com/r/arm64v8/known/)
- **Published image artifact details**:
[repo-info repo's `repos/known/` directory](https://github.com/docker-library/repo-info/blob/master/repos/known) ([history](https://github.com/docker-library/repo-info/commits/master/repos/known))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/known` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fknown)
[official-images repo's `library/known` file](https://github.com/docker-library/official-images/blob/master/library/known) ([history](https://github.com/docker-library/official-images/commits/master/library/known))
- **Source of this description**:
[docs repo's `known/` directory](https://github.com/docker-library/docs/tree/master/known) ([history](https://github.com/docker-library/docs/commits/master/known))
# Known: social publishing for groups and individuals
Blogging, meet social.
Known is a social publishing platform. Publish on your own site, reach your audience across social media.
![logo](https://raw.githubusercontent.com/docker-library/docs/817ab3c02e0a6c38fe8986c4ba96e23a9db26fab/known/logo.png)
# How to use this image
```bash
docker run --link some-mysql:db -d known
```
Now you can get access to fpm running on port 9000 inside the container. If you want to access it from the Internets, we recommend using a reverse proxy in front. You can find more information on that on the [docker-compose](#docker-compose) section.
The following environment variables are also honored for configuring your Known instance:
- `-e KNOWN_DB_HOST=...` (defaults to the IP and port of the linked `mysql` container)
- `-e KNOWN_DB_USER=...` (defaults to "root")
- `-e KNOWN_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked `mysql` container)
- `-e KNOWN_DB_NAME=...` (defaults to "known")
- `-e MAIL_HOST=...`
- `-e MAIL_PORT=...`
- `-e MAIL_SECURE=...` ("starttls" for instance)
- `-e MAIL_USER=...`
- `-e MAIL_PASS=...`
If the `KNOWN_DB_NAME` specified does not already exist on the given MySQL server, it will be created automatically upon startup of the `known` container, provided that the `KNOWN_DB_USER` specified has the necessary permissions to create it.
If you'd like to use an external database instead of a linked `mysql` container, specify the hostname and port with `KNOWN_DB_HOST` along with the password in `KNOWN_DB_PASSWORD` and the username in `KNOWN_DB_USER` (if it is something other than `root`):
```console
$ docker run --name some-known -e KNOWN_DB_HOST=10.1.2.3:3306 \
-e KNOWN_DB_USER=... -e KNOWN_DB_PASSWORD=... -d known
```
## Via docker-compose
You can use a setup that is used in production at [IndieHosters/known](https://github.com/indiehosters/known).
## Installation
Once started, you'll arrive at the configuration wizard. Follow the steps as indicated.
## Contribute
Pull requests are very welcome!
We'd love to hear your feedback and suggestions in the issue tracker: [github.com/idno/Known-docker/issues](https://github.com/idno/Known-docker/issues).
# License
View [license information](https://raw.githubusercontent.com/idno/Known/master/LICENSE) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `known/` directory](https://github.com/docker-library/repo-info/tree/master/repos/known).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

50
known/content.md
View File

@ -1,50 +0,0 @@
# Known: social publishing for groups and individuals
Blogging, meet social.
Known is a social publishing platform. Publish on your own site, reach your audience across social media.
%%LOGO%%
# How to use this image
```bash
docker run --link some-mysql:db -d %%IMAGE%%
```
Now you can get access to fpm running on port 9000 inside the container. If you want to access it from the Internets, we recommend using a reverse proxy in front. You can find more information on that on the [docker-compose](#docker-compose) section.
The following environment variables are also honored for configuring your Known instance:
- `-e KNOWN_DB_HOST=...` (defaults to the IP and port of the linked `mysql` container)
- `-e KNOWN_DB_USER=...` (defaults to "root")
- `-e KNOWN_DB_PASSWORD=...` (defaults to the value of the `MYSQL_ROOT_PASSWORD` environment variable from the linked `mysql` container)
- `-e KNOWN_DB_NAME=...` (defaults to "known")
- `-e MAIL_HOST=...`
- `-e MAIL_PORT=...`
- `-e MAIL_SECURE=...` ("starttls" for instance)
- `-e MAIL_USER=...`
- `-e MAIL_PASS=...`
If the `KNOWN_DB_NAME` specified does not already exist on the given MySQL server, it will be created automatically upon startup of the `%%REPO%%` container, provided that the `KNOWN_DB_USER` specified has the necessary permissions to create it.
If you'd like to use an external database instead of a linked `mysql` container, specify the hostname and port with `KNOWN_DB_HOST` along with the password in `KNOWN_DB_PASSWORD` and the username in `KNOWN_DB_USER` (if it is something other than `root`):
```console
$ docker run --name some-%%REPO%% -e KNOWN_DB_HOST=10.1.2.3:3306 \
-e KNOWN_DB_USER=... -e KNOWN_DB_PASSWORD=... -d %%REPO%%
```
## Via docker-compose
You can use a setup that is used in production at [IndieHosters/known](https://github.com/indiehosters/known).
## Installation
Once started, you'll arrive at the configuration wizard. Follow the steps as indicated.
## Contribute
Pull requests are very welcome!
We'd love to hear your feedback and suggestions in the issue tracker: [github.com/idno/Known-docker/issues](https://github.com/idno/Known-docker/issues).

1
known/deprecated.md
View File

@ -1 +0,0 @@
This image is deprecated due to inactivity (last updated Aug 2018; [docker-library/official-images#4670](https://github.com/docker-library/official-images/pull/4670)).

1
known/github-repo
View File

@ -1 +0,0 @@
https://github.com/idno/Known-Docker

1
known/license.md
View File

@ -1 +0,0 @@
View [license information](https://raw.githubusercontent.com/idno/Known/master/LICENSE) for the software contained in this image.

BIN
known/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 11 KiB

1
known/maintainer.md
View File

@ -1 +0,0 @@
[Known](%%GITHUB-REPO%%)

1
nuxeo/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; contact Nuxeo for support/updates

256
nuxeo/README.md
View File

@ -1,256 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "nuxeo/README.md"
IT IS AUTO-GENERATED
(from the other files in "nuxeo/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated, as the Nuxeo-maintained images are now private ([docker-library/official-images#6127 (comment)](https://github.com/docker-library/official-images/pull/6127#issuecomment-912530080)). For further support, contact [Nuxeo](https://www.nuxeo.com/).
# Quick reference
- **Maintained by**:
[Nuxeo](https://github.com/nuxeo/docker-nuxeo)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`7.10`, `7`, `LTS-2015`](https://github.com/nuxeo/docker-nuxeo/blob/f253a2398dbc39b42ca6ff84f2adeda8c1e8287e/7.10/Dockerfile)
- [`8.10`, `8`, `LTS-2016`](https://github.com/nuxeo/docker-nuxeo/blob/f253a2398dbc39b42ca6ff84f2adeda8c1e8287e/8.10/Dockerfile)
- [`9.10`, `9`, `LTS-2017`](https://github.com/nuxeo/docker-nuxeo/blob/f253a2398dbc39b42ca6ff84f2adeda8c1e8287e/9.10/Dockerfile)
- [`10.10`, `10`, `LTS-2019`, `LTS`, `FT`, `latest`](https://github.com/nuxeo/docker-nuxeo/blob/f253a2398dbc39b42ca6ff84f2adeda8c1e8287e/10.10/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/nuxeo/docker-nuxeo/issues](https://github.com/nuxeo/docker-nuxeo/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/nuxeo/)
- **Published image artifact details**:
[repo-info repo's `repos/nuxeo/` directory](https://github.com/docker-library/repo-info/blob/master/repos/nuxeo) ([history](https://github.com/docker-library/repo-info/commits/master/repos/nuxeo))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/nuxeo` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fnuxeo)
[official-images repo's `library/nuxeo` file](https://github.com/docker-library/official-images/blob/master/library/nuxeo) ([history](https://github.com/docker-library/official-images/commits/master/library/nuxeo))
- **Source of this description**:
[docs repo's `nuxeo/` directory](https://github.com/docker-library/docs/tree/master/nuxeo) ([history](https://github.com/docker-library/docs/commits/master/nuxeo))
# What is Nuxeo ?
The Nuxeo Platform is a highly customizable and extensible content management platform for building business applications.
![logo](https://raw.githubusercontent.com/docker-library/docs/6538ea62bab8b051d0556c689c113202d48089ed/nuxeo/logo.png)
# How to use this image
## Start a bare nuxeo instance
```console
$ docker run --name mynuxeo -p 8080:8080 -d nuxeo
```
This image includes `EXPOSE 8080` (the nuxeo port). The default Nuxeo configuration is applied which feature an embedded database (H2), and an embedded Elasticsearch instance. This setup is not suitable for production. See below to know how to setup a production ready container by specifying environment variables.
The Nuxeo platform is accesible at http://${DOCKER_HOST}:8080/ and default User and Password are Administrator/Administrator.
## Start a nuxeo with some additional packages
```console
$ docker run --name mynuxeo --rm -ti -p 8080:8080 -e NUXEO_PACKAGES="nuxeo-web-ui nuxeo-dam nuxeo-drive nuxeo-showcase-content nuxeo-template-rendering nuxeo-template-rendering-samples nuxeo-spreadsheet" nuxeo
```
This will install the same image as above but comes with some demo Nuxeo packages to demonstrate its various usage (DAM, DM, search etc...)
You can find additional informations on how to use this image in [Nuxeo documentation](https://doc.nuxeo.com/nxdoc/setting-up-your-nuxeo-environment/)
## Environment Variables
The Nuxeo image uses several environment variable that allow to specify a more specific setup.
### `NUXEO_DB_TYPE`
This defines the database type to use. By default it sets an H2 embedded database that is suitable for test purpose only. When specifying a DB type, other variable mays help :
- `NUXEO_DB_HOST` : If `NUXEO_DB_TYPE` is defined, this variable is mandatory and has to point to the DB server host.
- `NUXEO_DB_NAME` : name of the database to use (`nuxeo` by default)
- `NUXEO_DB_USER` : user to connect to the database (`nuxeo` by default)
- `NUXEO_DB_PASSWORD` : the password to connect to the database (`nuxeo` by default)
### `NUXEO_TEMPLATES`
This variables allows to add additional [Nuxeo configuration templates](https://doc.nuxeo.com/x/0AB9) in the `nuxeo.templates` configuration variable.
### `NUXEO_ES_HOSTS`
This variables allows to setup an external Elasticsearch cluster. Use a comma separated list of Elasticsearch hosts with the 9300 port. Additional environment vars may be setup like :
- `NUXEO_ES_CLUSTER_NAME` : name of the Elasticsearch cluster to join
- `NUXEO_ES_INDEX_NAME`: name of the index (`nuxeo` by default)
- `NUXEO_ES_REPLICAS` : number or replicas (`1` by default). If not 0, it means that your ES cluster must have enough node to fullfill the replicas setup.
- `NUXEO_ES_SHARDS` : number or shards (`5` by default).
For instance :
NUXEO_ES_HOSTS=es1:9300,es2:9300
NUXEO_ES_CLUSTER_NAME=dockerCluster
NUXEO_ES_INDEX_NAME=nuxeo1
NUXEO_ES_REPLICAS=0
NUXEO_ES_SHARDS=5
### `NUXEO_REDIS_HOST`
In order to use Redis, just set up this variable to the Redis host address.
### `NUXEO_REDIS_PORT`
If Redis is setup, you can ovewrite the default port configuration (default to 6379)
### `NUXEO_CLID`
Allow to setup a CLID for Nuxeo Connect registration. This parameter is in the form `part1\npart2`, so depending on the environment you may have to escape the `\` character.
You can find additional informations the registration process in the [Nuxeo documentation](https://doc.nuxeo.com/nxdoc/setting-up-your-nuxeo-environment/)
### `NUXEO_INSTALL_HOTFIX`
This launch the install of latest Hotfixes. (`true` by default, but needs a `NUXEO_CLID` to be setup)
### `NUXEO_PACKAGES`
Allows to install [Nuxeo packages](https://doc.nuxeo.com/x/aAfF) at startup.
### `NUXEO_URL`
This variable sets the URL where your Nuxeo instance will be joinable. It's used for instance to refer to it when sending server's address in mails.
### `NUXEO_DATA`
Location of the Nuxeo data directory. (`/var/lib/nuxeo/data` by default). You will likely customize NUXEO_DATA to map it on docker volume so data like binaries stay persistent.
### `NUXEO_LOG`
Location of the Nuxeo log directory. (`/var/log/nuxeo` by default)
### `NUXEO_AUTOMATION_TRACE`
If set to "true", this will enable the [automation trace mode](https://doc.nuxeo.com/display/NXDOC/Automation+Tracing).
### `NUXEO_DEV_MODE`
If set to "true", this will enable the development mode that will allow [hot reload](https://doc.nuxeo.com/display/CORG/Supporting+Hot+Reload) when developing with [Nuxeo Studio](http://www.nuxeo.com/products/studio/).
### `NUXEO_BINARY_STORE`
Tells the location of the binary store which configure the [binary storage](https://doc.nuxeo.com/x/fYYZAQ)
### `NUXEO_TRANSIENT_STORE`
Tells the location of [the transient storage](http://doc.nuxeo.com/display/NXDOC/Transient+Store)
### `NUXEO_DDL_MODE`
Allows to setup [Database creation option](https://doc.nuxeo.com/x/hwQz#RepositoryConfiguration-DatabaseCreationOption) by fixing the `ddlMode` value.
### `NUXEO_CUSTOM_PARAM`
Allows to add custom parameters to `nuxeo.conf`. Multiple parameters can be splitted by a `\n`. For instance:
NUXEO_CUSTOM_PARAM="repository.clustering.enabled=false\nrepository.clustering.delay=1000"
# How to extend this image
## Adding additional configuration
If you would like to do additional setup in an image derived from this one, you can add a `/docker-entrypoint-initnuxeo.d/nuxeo.conf` file that will be appended to the end of the regular `nuxeo.conf` file.
```dockerfile
FROM nuxeo:7.10
COPY nuxeo.conf /docker-entrypoint-initnuxeo.d/nuxeo.conf
```
If you need a root account to run some installation steps in your `Dockerfile`, then you need to put those steps between two `USER` command as the image is run with the user `1000` (nuxeo). For instance:
```dockerfile
FROM nuxeo:LTS
USER root
RUN apt-get update && apt-get install -y --no-install-recommends vim
USER 1000
```
## Launching custom shell scripts
You can add your own shell scripts in a special `/docker-entrypoint-initnuxeo.d` directory. When ending in `.sh`, they will be run on default entrypoint startup.
## ffmpeg
As it contains some non-free Codecs, we dont't ship a binary version of `ffmpeg` as part of this image. However, you can simply add the compilation in a derived images by adding these lines to your Dockerfile.
```dockerfile
FROM nuxeo:7.10
USER root
RUN echo "deb http://httpredir.debian.org/debian jessie non-free" >> /etc/apt/sources.list
RUN apt-get update && apt-get install -y --no-install-recommends libfaac-dev git
WORKDIR /tmp
# Build ffmpeg
ENV BUILD_YASM true
ENV LIBFAAC true
RUN git clone https://github.com/nuxeo/ffmpeg-nuxeo.git
WORKDIR ffmpeg-nuxeo
RUN ./prepare-packages.sh \
&& ./build-yasm.sh \
&& ./build-x264.sh \
&& ./build-libvpx.sh \
&& ./build-ffmpeg.sh \
&& cd /tmp \
&& rm -Rf ffmpeg-nuxeo \
&& rm -rf /var/lib/apt/lists/*
USER 1000
```
## Using Oracle JVM
For the same reasons as `ffmpeg` we don't ship the Oracle JVM and rely by default on OpenJDK. If you want to use the Hotspot JVM you cans add the following lines in a derived Dockerfile
```dockerfile
RUN apt-get remove -y --purge openjdk-8-jdk \
&& add-apt-repository -y ppa:webupd8team/java && apt-get update \
&& echo "debconf shared/accepted-oracle-license-v1-1 select true" | debconf-set-selections \
&& echo "debconf shared/accepted-oracle-license-v1-1 seen true" | debconf-set-selections \
&& apt-get install -y oracle-java8-installer \
&& rm -rf /var/lib/apt/lists/*
```
## Why is this images so big ?
This image is big because it contains a lot of features. The nuxeo distribution itself is about 250M and in order to make cool things work like generating thumbnails or converting document to PDF we need some additional tools that are bundled in the image. We hope that in the future we will be able to delegate those conversions to external services that would be bundled as additional docker images.
# License
View [license information](http://doc.nuxeo.com/x/gIK7) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `nuxeo/` directory](https://github.com/docker-library/repo-info/tree/master/repos/nuxeo).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

192
nuxeo/content.md
View File

@ -1,192 +0,0 @@
# What is Nuxeo ?
The Nuxeo Platform is a highly customizable and extensible content management platform for building business applications.
%%LOGO%%
# How to use this image
## Start a bare nuxeo instance
```console
$ docker run --name mynuxeo -p 8080:8080 -d %%IMAGE%%
```
This image includes `EXPOSE 8080` (the nuxeo port). The default Nuxeo configuration is applied which feature an embedded database (H2), and an embedded Elasticsearch instance. This setup is not suitable for production. See below to know how to setup a production ready container by specifying environment variables.
The Nuxeo platform is accesible at http://${DOCKER_HOST}:8080/ and default User and Password are Administrator/Administrator.
## Start a nuxeo with some additional packages
```console
$ docker run --name mynuxeo --rm -ti -p 8080:8080 -e NUXEO_PACKAGES="nuxeo-web-ui nuxeo-dam nuxeo-drive nuxeo-showcase-content nuxeo-template-rendering nuxeo-template-rendering-samples nuxeo-spreadsheet" nuxeo
```
This will install the same image as above but comes with some demo Nuxeo packages to demonstrate its various usage (DAM, DM, search etc...)
You can find additional informations on how to use this image in [Nuxeo documentation](https://doc.nuxeo.com/nxdoc/setting-up-your-nuxeo-environment/)
## Environment Variables
The Nuxeo image uses several environment variable that allow to specify a more specific setup.
### `NUXEO_DB_TYPE`
This defines the database type to use. By default it sets an H2 embedded database that is suitable for test purpose only. When specifying a DB type, other variable mays help :
- `NUXEO_DB_HOST` : If `NUXEO_DB_TYPE` is defined, this variable is mandatory and has to point to the DB server host.
- `NUXEO_DB_NAME` : name of the database to use (`nuxeo` by default)
- `NUXEO_DB_USER` : user to connect to the database (`nuxeo` by default)
- `NUXEO_DB_PASSWORD` : the password to connect to the database (`nuxeo` by default)
### `NUXEO_TEMPLATES`
This variables allows to add additional [Nuxeo configuration templates](https://doc.nuxeo.com/x/0AB9) in the `nuxeo.templates` configuration variable.
### `NUXEO_ES_HOSTS`
This variables allows to setup an external Elasticsearch cluster. Use a comma separated list of Elasticsearch hosts with the 9300 port. Additional environment vars may be setup like :
- `NUXEO_ES_CLUSTER_NAME` : name of the Elasticsearch cluster to join
- `NUXEO_ES_INDEX_NAME`: name of the index (`nuxeo` by default)
- `NUXEO_ES_REPLICAS` : number or replicas (`1` by default). If not 0, it means that your ES cluster must have enough node to fullfill the replicas setup.
- `NUXEO_ES_SHARDS` : number or shards (`5` by default).
For instance :
NUXEO_ES_HOSTS=es1:9300,es2:9300
NUXEO_ES_CLUSTER_NAME=dockerCluster
NUXEO_ES_INDEX_NAME=nuxeo1
NUXEO_ES_REPLICAS=0
NUXEO_ES_SHARDS=5
### `NUXEO_REDIS_HOST`
In order to use Redis, just set up this variable to the Redis host address.
### `NUXEO_REDIS_PORT`
If Redis is setup, you can ovewrite the default port configuration (default to 6379)
### `NUXEO_CLID`
Allow to setup a CLID for Nuxeo Connect registration. This parameter is in the form `part1\npart2`, so depending on the environment you may have to escape the `\` character.
You can find additional informations the registration process in the [Nuxeo documentation](https://doc.nuxeo.com/nxdoc/setting-up-your-nuxeo-environment/)
### `NUXEO_INSTALL_HOTFIX`
This launch the install of latest Hotfixes. (`true` by default, but needs a `NUXEO_CLID` to be setup)
### `NUXEO_PACKAGES`
Allows to install [Nuxeo packages](https://doc.nuxeo.com/x/aAfF) at startup.
### `NUXEO_URL`
This variable sets the URL where your Nuxeo instance will be joinable. It's used for instance to refer to it when sending server's address in mails.
### `NUXEO_DATA`
Location of the Nuxeo data directory. (`/var/lib/nuxeo/data` by default). You will likely customize NUXEO_DATA to map it on docker volume so data like binaries stay persistent.
### `NUXEO_LOG`
Location of the Nuxeo log directory. (`/var/log/nuxeo` by default)
### `NUXEO_AUTOMATION_TRACE`
If set to "true", this will enable the [automation trace mode](https://doc.nuxeo.com/display/NXDOC/Automation+Tracing).
### `NUXEO_DEV_MODE`
If set to "true", this will enable the development mode that will allow [hot reload](https://doc.nuxeo.com/display/CORG/Supporting+Hot+Reload) when developing with [Nuxeo Studio](http://www.nuxeo.com/products/studio/).
### `NUXEO_BINARY_STORE`
Tells the location of the binary store which configure the [binary storage](https://doc.nuxeo.com/x/fYYZAQ)
### `NUXEO_TRANSIENT_STORE`
Tells the location of [the transient storage](http://doc.nuxeo.com/display/NXDOC/Transient+Store)
### `NUXEO_DDL_MODE`
Allows to setup [Database creation option](https://doc.nuxeo.com/x/hwQz#RepositoryConfiguration-DatabaseCreationOption) by fixing the `ddlMode` value.
### `NUXEO_CUSTOM_PARAM`
Allows to add custom parameters to `nuxeo.conf`. Multiple parameters can be splitted by a `\n`. For instance:
NUXEO_CUSTOM_PARAM="repository.clustering.enabled=false\nrepository.clustering.delay=1000"
# How to extend this image
## Adding additional configuration
If you would like to do additional setup in an image derived from this one, you can add a `/docker-entrypoint-initnuxeo.d/nuxeo.conf` file that will be appended to the end of the regular `nuxeo.conf` file.
```dockerfile
FROM %%IMAGE%%:7.10
COPY nuxeo.conf /docker-entrypoint-initnuxeo.d/nuxeo.conf
```
If you need a root account to run some installation steps in your `Dockerfile`, then you need to put those steps between two `USER` command as the image is run with the user `1000` (nuxeo). For instance:
```dockerfile
FROM %%IMAGE%%:LTS
USER root
RUN apt-get update && apt-get install -y --no-install-recommends vim
USER 1000
```
## Launching custom shell scripts
You can add your own shell scripts in a special `/docker-entrypoint-initnuxeo.d` directory. When ending in `.sh`, they will be run on default entrypoint startup.
## ffmpeg
As it contains some non-free Codecs, we dont't ship a binary version of `ffmpeg` as part of this image. However, you can simply add the compilation in a derived images by adding these lines to your Dockerfile.
```dockerfile
FROM %%IMAGE%%:7.10
USER root
RUN echo "deb http://httpredir.debian.org/debian jessie non-free" >> /etc/apt/sources.list
RUN apt-get update && apt-get install -y --no-install-recommends libfaac-dev git
WORKDIR /tmp
# Build ffmpeg
ENV BUILD_YASM true
ENV LIBFAAC true
RUN git clone https://github.com/nuxeo/ffmpeg-nuxeo.git
WORKDIR ffmpeg-nuxeo
RUN ./prepare-packages.sh \
&& ./build-yasm.sh \
&& ./build-x264.sh \
&& ./build-libvpx.sh \
&& ./build-ffmpeg.sh \
&& cd /tmp \
&& rm -Rf ffmpeg-nuxeo \
&& rm -rf /var/lib/apt/lists/*
USER 1000
```
## Using Oracle JVM
For the same reasons as `ffmpeg` we don't ship the Oracle JVM and rely by default on OpenJDK. If you want to use the Hotspot JVM you cans add the following lines in a derived Dockerfile
```dockerfile
RUN apt-get remove -y --purge openjdk-8-jdk \
&& add-apt-repository -y ppa:webupd8team/java && apt-get update \
&& echo "debconf shared/accepted-oracle-license-v1-1 select true" | debconf-set-selections \
&& echo "debconf shared/accepted-oracle-license-v1-1 seen true" | debconf-set-selections \
&& apt-get install -y oracle-java8-installer \
&& rm -rf /var/lib/apt/lists/*
```
## Why is this images so big ?
This image is big because it contains a lot of features. The nuxeo distribution itself is about 250M and in order to make cool things work like generating thumbnails or converting document to PDF we need some additional tools that are bundled in the image. We hope that in the future we will be able to delegate those conversions to external services that would be bundled as additional docker images.

1
nuxeo/deprecated.md
View File

@ -1 +0,0 @@
This image is deprecated, as the Nuxeo-maintained images are now private ([docker-library/official-images#6127 (comment)](https://github.com/docker-library/official-images/pull/6127#issuecomment-912530080)). For further support, contact [Nuxeo](https://www.nuxeo.com/).

1
nuxeo/github-repo
View File

@ -1 +0,0 @@
https://github.com/nuxeo/docker-nuxeo

1
nuxeo/license.md
View File

@ -1 +0,0 @@
View [license information](http://doc.nuxeo.com/x/gIK7) for the software contained in this image.

BIN
nuxeo/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 1.8 KiB

1
nuxeo/maintainer.md
View File

@ -1 +0,0 @@
[Nuxeo](%%GITHUB-REPO%%)

1
opensuse/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; for current images by the openSUSE Project see opensuse/leap and opensuse/tumbleweed.

85
opensuse/README.md
View File

@ -1,85 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "opensuse/README.md"
IT IS AUTO-GENERATED
(from the other files in "opensuse/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
These images were removed in favor of the [`opensuse/leap`](https://hub.docker.com/r/opensuse/leap) and [`opensuse/tumbleweed`](https://hub.docker.com/r/opensuse/tumbleweed) images provided and maintained by the [openSUSE Project](https://www.opensuse.org/) release team.
An archive for images of unsupported versions can be found at [`opensuse/archive`](https://hub.docker.com/r/opensuse/archive).
# Quick reference
- **Maintained by**:
[the SUSE containers team](https://github.com/openSUSE/docker-containers-build)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
**No supported tags**
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/openSUSE/docker-containers-build/issues](https://github.com/openSUSE/docker-containers-build/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
**No supported architectures**
- **Published image artifact details**:
[repo-info repo's `repos/opensuse/` directory](https://github.com/docker-library/repo-info/blob/master/repos/opensuse) ([history](https://github.com/docker-library/repo-info/commits/master/repos/opensuse))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/opensuse` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fopensuse)
[official-images repo's `library/opensuse` file](https://github.com/docker-library/official-images/blob/master/library/opensuse) ([history](https://github.com/docker-library/official-images/commits/master/library/opensuse))
- **Source of this description**:
[docs repo's `opensuse/` directory](https://github.com/docker-library/docs/tree/master/opensuse) ([history](https://github.com/docker-library/docs/commits/master/opensuse))
# openSUSE
This project contains the stable releases of the openSUSE distribution.
# Naming conventions
Each image is tagged using both the release number (eg *"13.1"*) and the code name (eg *"Bottle"*). The latest stable release is always available using the "*latest*" tag.
# Building
These images are generated using [KIWI](https://github.com/openSUSE/kiwi). Their source file can be found on [this repository](https://github.com/openSUSE/docker-containers).
# Repositories and packages
The package selection is kept minimal to reduce the footprint of the image.
However the following repositories are already part of the image:
- OSS
- OSS Updates
- Non-OSS
- Non-OSS Updates
# License
View the [license information](https://en.opensuse.org/openSUSE:License) for the software contained in this image. Please note that individual packages installed may have their own licenses, which you also must follow. License information is available through the built-in package manager.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `opensuse/` directory](https://github.com/docker-library/repo-info/tree/master/repos/opensuse).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

22
opensuse/content.md
View File

@ -1,22 +0,0 @@
# openSUSE
This project contains the stable releases of the openSUSE distribution.
# Naming conventions
Each image is tagged using both the release number (eg *"13.1"*) and the code name (eg *"Bottle"*). The latest stable release is always available using the "*latest*" tag.
# Building
These images are generated using [KIWI](https://github.com/openSUSE/kiwi). Their source file can be found on [this repository](https://github.com/openSUSE/docker-containers).
# Repositories and packages
The package selection is kept minimal to reduce the footprint of the image.
However the following repositories are already part of the image:
- OSS
- OSS Updates
- Non-OSS
- Non-OSS Updates

3
opensuse/deprecated.md
View File

@ -1,3 +0,0 @@
These images were removed in favor of the [`opensuse/leap`](https://hub.docker.com/r/opensuse/leap) and [`opensuse/tumbleweed`](https://hub.docker.com/r/opensuse/tumbleweed) images provided and maintained by the [openSUSE Project](https://www.opensuse.org/) release team.
An archive for images of unsupported versions can be found at [`opensuse/archive`](https://hub.docker.com/r/opensuse/archive).

1
opensuse/github-repo
View File

@ -1 +0,0 @@
https://github.com/openSUSE/docker-containers-build

1
opensuse/license.md
View File

@ -1 +0,0 @@
View the [license information](https://en.opensuse.org/openSUSE:License) for the software contained in this image. Please note that individual packages installed may have their own licenses, which you also must follow. License information is available through the built-in package manager.

BIN
opensuse/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 23 KiB

1
opensuse/maintainer.md
View File

@ -1 +0,0 @@
[the SUSE containers team](%%GITHUB-REPO%%)

1
rapidoid/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

199
rapidoid/README.md
View File

@ -1,199 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "rapidoid/README.md"
IT IS AUTO-GENERATED
(from the other files in "rapidoid/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to inactivity (last updated Aug 2018; [docker-library/official-images#4667](https://github.com/docker-library/official-images/pull/4667)).
As noted in [docker-library/official-images#4667 (comment)](https://github.com/docker-library/official-images/pull/4667#issuecomment-565220107), it will likely see updates again when Rapidoid 6 is released.
# Quick reference
- **Maintained by**:
[Rapidoid](https://github.com/rapidoid/docker-rapidoid)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`5.4.6`, `5.4`, `5`, `latest`](https://github.com/rapidoid/docker-rapidoid/blob/8fbb45c706fec5b0a015a37c24862127180ae9e9/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/rapidoid/docker-rapidoid/issues](https://github.com/rapidoid/docker-rapidoid/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/rapidoid/), [`arm64v8`](https://hub.docker.com/r/arm64v8/rapidoid/)
- **Published image artifact details**:
[repo-info repo's `repos/rapidoid/` directory](https://github.com/docker-library/repo-info/blob/master/repos/rapidoid) ([history](https://github.com/docker-library/repo-info/commits/master/repos/rapidoid))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/rapidoid` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Frapidoid)
[official-images repo's `library/rapidoid` file](https://github.com/docker-library/official-images/blob/master/library/rapidoid) ([history](https://github.com/docker-library/official-images/commits/master/library/rapidoid))
- **Source of this description**:
[docs repo's `rapidoid/` directory](https://github.com/docker-library/docs/tree/master/rapidoid) ([history](https://github.com/docker-library/docs/commits/master/rapidoid))
# What is Rapidoid?
Rapidoid is an extremely fast HTTP server and modern Java web framework / application container, with a strong focus on high productivity and high performance.
> [www.rapidoid.org](http://www.rapidoid.org)
![logo](https://raw.githubusercontent.com/docker-library/docs/7fc38a6e22991477a231ce556a7f2860623afb67/rapidoid/logo.png)
# How to use this image
To quickly start Rapidoid and display some basic usage help, run:
```console
$ docker run --rm rapidoid --help
```
Rapidoid can be used in different ways:
- as a web tool, to quickly prototype RESTful web services from the command line
- as a HTTP server, to serve static resources
- as a Java web application framework/container, to deploy a web application JAR
## Quickly prototyping SQL-powered RESTful web services
To quickly prototype SQL-powered RESTful web services from the command line, you need to link the database container to the Rapidoid container. The MySQL containers should be linked under name `mysql`, and PostgreSQL containers under name `postgres`.
This example starts a new MySQL container and links it under name `mysql` in the Rapidoid container, where a RESTful service is defined by specifying SQL query for the route `GET /users`. The service returns the result (a list of MySQL users) in JSON format.
```console
docker run -d --name some-mysql -e MYSQL_ROOT_PASSWORD=db-pass mysql
docker run -it --rm \
-p 8888:8888 \
--link some-mysql:mysql \
rapidoid \
profiles=mysql \
jdbc.host=mysql \
jdbc.password=db-pass \
'/users <= SELECT user FROM mysql.user'
```
**Note:** Please wait for several seconds for the MySQL database to initialize, and then you can visit [http://localhost:8888/users](http://localhost:8888/users) (or `http://your-host:8888/users`) in your web browser.
**Syntax for the service prototyping arguments**:
```console
'[GET|POST|PUT|DELETE|PATCH] <uri> <= <sql>'
```
## Serving static files
Rapidoid will automatically serve static files from the folders: `/app/static`. To serve the contents of the `/your-www-root` directory, please mount it as `/app/static`:
```console
$ docker run -it --rm \
-p 8888:8888 \
-v /your-www-root:/app/static \
rapidoid
```
## Configuration
Rapidoid will try to read the configuration from `/app/config.yml`. The configuration can also be specified with command-line arguments or environment variables.
To configure a custom port (by default `8888`) for the default and the Admin server, run the following command. If `rapidoid-admin.port` is not configured, the default server is also used as Admin server, so only one port will be opened (`rapidoid.port`).
```console
$ docker run -it --rm \
-p 4444:4444 \
-p 9999:9999 \
rapidoid \
rapidoid.port=4444 \
rapidoid-admin.port=9999 \
app.services=ping \
admin.services=status
```
Then you can visit [http://localhost:4444/\_ping](http://localhost:4444/_ping) (or `http://your-host:4444/_ping`) and [http://localhost:9999/\_status](http://localhost:9999/_status) (or `http://your-host:9999/_status`) in your web browser.
The same setup can be configured with environment variables:
```console
$ docker run -it --rm \
-p 4444:4444 \
-p 9999:9999 \
-e RAPIDOID_PORT=4444 \
-e RAPIDOID-ADMIN_PORT=9999 \
rapidoid \
app.services=ping \
admin.services=status
```
For more details, please see the [full list of configuration options and their default values](http://www.rapidoid.org/the-default-configuration.html).
## Security
Rapidoid's HMAC-based security token mechanism requires all containers to share the same secret key when scaling out a web application:
```console
$ docker run -it --rm \
-p 8888:8888 \
-e SECRET=your-secret-key \
rapidoid
```
While this is an easy way to get started, for security reasons it is recommended to store the secret key in the `/app/config.yml` file, with proper permissions.
**Note:** For production use, you must replace `your-secret-key` with a real, private secret key.
**Note:** If no secret key is specified, a random secret key will be generated, which is acceptable when deploying a single container.
## Full bootstrap of Rapidoid's Admin Center
To bootstrap a full-blown Admin Center in Rapidoid, you will also need to configure a password for the built-in `admin` user:
```console
$ docker run -d \
--restart=always \
-p 8888:8888 \
-e SECRET=your-secret-key \
-e USERS_ADMIN_PASSWORD=admin-pass \
rapidoid \
admin.services=center
```
Please replace `admin-pass` with a real password for the `admin` user. Then you can login to the Admin Center by visiting [http://localhost:8888/\_](http://localhost:8888/_) (or `http://your-host:8888/_`) in your web browser.
**Note:** For production use, you must replace `your-secret-key` with a real, private secret key (please see the `Security` section).
# How to extend this image (application JAR deployment)
To use this image as base image for your web application, simply add your application JAR as `/app/app.jar`:
```dockerfile
COPY <location/of/your/webapp.jar> /app/app.jar
```
# License
View [license information](https://www.apache.org/licenses/LICENSE-2.0) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `rapidoid/` directory](https://github.com/docker-library/repo-info/tree/master/repos/rapidoid).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

136
rapidoid/content.md
View File

@ -1,136 +0,0 @@
# What is Rapidoid?
Rapidoid is an extremely fast HTTP server and modern Java web framework / application container, with a strong focus on high productivity and high performance.
> [www.rapidoid.org](http://www.rapidoid.org)
%%LOGO%%
# How to use this image
To quickly start Rapidoid and display some basic usage help, run:
```console
$ docker run --rm %%IMAGE%% --help
```
Rapidoid can be used in different ways:
- as a web tool, to quickly prototype RESTful web services from the command line
- as a HTTP server, to serve static resources
- as a Java web application framework/container, to deploy a web application JAR
## Quickly prototyping SQL-powered RESTful web services
To quickly prototype SQL-powered RESTful web services from the command line, you need to link the database container to the Rapidoid container. The MySQL containers should be linked under name `mysql`, and PostgreSQL containers under name `postgres`.
This example starts a new MySQL container and links it under name `mysql` in the Rapidoid container, where a RESTful service is defined by specifying SQL query for the route `GET /users`. The service returns the result (a list of MySQL users) in JSON format.
```console
docker run -d --name some-mysql -e MYSQL_ROOT_PASSWORD=db-pass mysql
docker run -it --rm \
-p 8888:8888 \
--link some-mysql:mysql \
%%REPO%% \
profiles=mysql \
jdbc.host=mysql \
jdbc.password=db-pass \
'/users <= SELECT user FROM mysql.user'
```
**Note:** Please wait for several seconds for the MySQL database to initialize, and then you can visit [http://localhost:8888/users](http://localhost:8888/users) (or `http://your-host:8888/users`) in your web browser.
**Syntax for the service prototyping arguments**:
```console
'[GET|POST|PUT|DELETE|PATCH] <uri> <= <sql>'
```
## Serving static files
Rapidoid will automatically serve static files from the folders: `/app/static`. To serve the contents of the `/your-www-root` directory, please mount it as `/app/static`:
```console
$ docker run -it --rm \
-p 8888:8888 \
-v /your-www-root:/app/static \
%%REPO%%
```
## Configuration
Rapidoid will try to read the configuration from `/app/config.yml`. The configuration can also be specified with command-line arguments or environment variables.
To configure a custom port (by default `8888`) for the default and the Admin server, run the following command. If `rapidoid-admin.port` is not configured, the default server is also used as Admin server, so only one port will be opened (`rapidoid.port`).
```console
$ docker run -it --rm \
-p 4444:4444 \
-p 9999:9999 \
%%REPO%% \
rapidoid.port=4444 \
rapidoid-admin.port=9999 \
app.services=ping \
admin.services=status
```
Then you can visit [http://localhost:4444/\_ping](http://localhost:4444/_ping) (or `http://your-host:4444/_ping`) and [http://localhost:9999/\_status](http://localhost:9999/_status) (or `http://your-host:9999/_status`) in your web browser.
The same setup can be configured with environment variables:
```console
$ docker run -it --rm \
-p 4444:4444 \
-p 9999:9999 \
-e RAPIDOID_PORT=4444 \
-e RAPIDOID-ADMIN_PORT=9999 \
%%REPO%% \
app.services=ping \
admin.services=status
```
For more details, please see the [full list of configuration options and their default values](http://www.rapidoid.org/the-default-configuration.html).
## Security
Rapidoid's HMAC-based security token mechanism requires all containers to share the same secret key when scaling out a web application:
```console
$ docker run -it --rm \
-p 8888:8888 \
-e SECRET=your-secret-key \
%%REPO%%
```
While this is an easy way to get started, for security reasons it is recommended to store the secret key in the `/app/config.yml` file, with proper permissions.
**Note:** For production use, you must replace `your-secret-key` with a real, private secret key.
**Note:** If no secret key is specified, a random secret key will be generated, which is acceptable when deploying a single container.
## Full bootstrap of Rapidoid's Admin Center
To bootstrap a full-blown Admin Center in Rapidoid, you will also need to configure a password for the built-in `admin` user:
```console
$ docker run -d \
--restart=always \
-p 8888:8888 \
-e SECRET=your-secret-key \
-e USERS_ADMIN_PASSWORD=admin-pass \
%%REPO%% \
admin.services=center
```
Please replace `admin-pass` with a real password for the `admin` user. Then you can login to the Admin Center by visiting [http://localhost:8888/\_](http://localhost:8888/_) (or `http://your-host:8888/_`) in your web browser.
**Note:** For production use, you must replace `your-secret-key` with a real, private secret key (please see the `Security` section).
# How to extend this image (application JAR deployment)
To use this image as base image for your web application, simply add your application JAR as `/app/app.jar`:
```dockerfile
COPY <location/of/your/webapp.jar> /app/app.jar
```

3
rapidoid/deprecated.md
View File

@ -1,3 +0,0 @@
This image is deprecated due to inactivity (last updated Aug 2018; [docker-library/official-images#4667](https://github.com/docker-library/official-images/pull/4667)).
As noted in [docker-library/official-images#4667 (comment)](https://github.com/docker-library/official-images/pull/4667#issuecomment-565220107), it will likely see updates again when Rapidoid 6 is released.

1
rapidoid/github-repo
View File

@ -1 +0,0 @@
https://github.com/rapidoid/docker-rapidoid

1
rapidoid/license.md
View File

@ -1 +0,0 @@
View [license information](https://www.apache.org/licenses/LICENSE-2.0) for the software contained in this image.

BIN
rapidoid/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 17 KiB

1
rapidoid/maintainer.md
View File

@ -1 +0,0 @@
[Rapidoid](%%GITHUB-REPO%%)

1
sentry/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; https://develop.sentry.dev/self-hosted/

163
sentry/README.md
View File

@ -1,163 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "sentry/README.md"
IT IS AUTO-GENERATED
(from the other files in "sentry/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated in favor of the full installation explained over at [Self-Hosted Sentry Docs](https://develop.sentry.dev/self-hosted/) (last updated July 2019; [getsentry/docker-sentry#189](https://github.com/getsentry/docker-sentry/pull/189)).
# Quick reference
- **Maintained by**:
[Sentry](https://github.com/getsentry/docker-sentry)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
**No supported tags**
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/getsentry/docker-sentry/issues](https://github.com/getsentry/docker-sentry/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
**No supported architectures**
- **Published image artifact details**:
[repo-info repo's `repos/sentry/` directory](https://github.com/docker-library/repo-info/blob/master/repos/sentry) ([history](https://github.com/docker-library/repo-info/commits/master/repos/sentry))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/sentry` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fsentry)
[official-images repo's `library/sentry` file](https://github.com/docker-library/official-images/blob/master/library/sentry) ([history](https://github.com/docker-library/official-images/commits/master/library/sentry))
- **Source of this description**:
[docs repo's `sentry/` directory](https://github.com/docker-library/docs/tree/master/sentry) ([history](https://github.com/docker-library/docs/commits/master/sentry))
# What is Sentry?
Sentry is a realtime event logging and aggregation platform. It specializes in monitoring errors and extracting all the information needed to do a proper post-mortem without any of the hassle of the standard user feedback loop.
> [github.com/getsentry/sentry](https://github.com/getsentry/sentry)
![logo](https://raw.githubusercontent.com/docker-library/docs/7d1c6fff37893bcefc186de7b978f5bdb2f801f6/sentry/logo.png)
# How to use this image
## How to setup a full Sentry instance
1. Start a Redis container
```console
$ docker run -d --name sentry-redis redis
```
2. Start a Postgres container
```console
$ docker run -d --name sentry-postgres -e POSTGRES_PASSWORD=secret -e POSTGRES_USER=sentry postgres
```
3. Generate a new secret key to be shared by all `sentry` containers. This value will then be used as the `SENTRY_SECRET_KEY` environment variable.
```console
$ docker run --rm sentry config generate-secret-key
```
4. If this is a new database, you'll need to run `upgrade`
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry upgrade
```
**Note: the `-it` is important as the initial upgrade will prompt to create an initial user and will fail without it**
5. Now start up Sentry server
```console
$ docker run -d --name my-sentry -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres sentry
```
6. The default config needs a celery beat and celery workers, start as many workers as you need (each with a unique name)
```console
$ docker run -d --name sentry-cron -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry run cron
$ docker run -d --name sentry-worker-1 -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis sentry run worker
```
### Port mapping
If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used. Just add `-p 8080:9000` to the `docker run` arguments and then access either `http://localhost:8080` or `http://host-ip:8080` in a browser.
## Configuring the initial user
If you did not create a superuser during `upgrade`, use the following to create one:
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres sentry createuser
```
## Environment variables
When you start the `sentry` image, you can adjust the configuration of the Sentry instance by passing one or more environment variables on the `docker run` command line. Please note that these environment variables are provided as a jump start, and it's highly recommended to either mount in your own config file or utilize the `sentry:onbuild` variant.
### `SENTRY_SECRET_KEY`
A secret key used for cryptographic functions within Sentry. This key should be unique and consistent across all running instances. You can generate a new secret key doing something like:
```console
$ docker run --rm sentry config generate-secret-key
```
### `SENTRY_POSTGRES_HOST`, `SENTRY_POSTGRES_PORT`, `SENTRY_DB_NAME`, `SENTRY_DB_USER`, `SENTRY_DB_PASSWORD`
Database credentials for your Postgres server. These values aren't needed if a linked `postgres` container exists.
### `SENTRY_REDIS_HOST`, `SENTRY_REDIS_PORT`, `SENTRY_REDIS_DB`
Connection information for your Redis server. These values aren't needed if a linked `redis` container exists.
### `SENTRY_MEMCACHED_HOST`, `SENTRY_MEMCACHED_PORT`
Connection information for a Memcache server. These values aren't needed if a linked `memcached` container exists.
### `SENTRY_FILESTORE_DIR`
Directory where uploaded files will be stored. This defaults to `/var/lib/sentry/files` and is a `VOLUME` for persistent data.
### `SENTRY_SERVER_EMAIL`
The email address used for `From:` in outbound emails. Default: `root@localhost`
### `SENTRY_EMAIL_HOST`, `SENTRY_EMAIL_PORT`, `SENTRY_EMAIL_USER`, `SENTRY_EMAIL_PASSWORD`, `SENTRY_EMAIL_USE_TLS`
Connection information for an outbound smtp server. These values aren't needed if a linked `smtp` container exists.
### `SENTRY_MAILGUN_API_KEY`
If you're using Mailgun for inbound mail, set your API key and configure a route to forward to `/api/hooks/mailgun/inbound/`.
# License
View [license information](https://github.com/getsentry/sentry/blob/master/LICENSE) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `sentry/` directory](https://github.com/docker-library/repo-info/tree/master/repos/sentry).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

102
sentry/content.md
View File

@ -1,102 +0,0 @@
# What is Sentry?
Sentry is a realtime event logging and aggregation platform. It specializes in monitoring errors and extracting all the information needed to do a proper post-mortem without any of the hassle of the standard user feedback loop.
> [github.com/getsentry/sentry](https://github.com/getsentry/sentry)
%%LOGO%%
# How to use this image
## How to setup a full Sentry instance
1. Start a Redis container
```console
$ docker run -d --name sentry-redis redis
```
2. Start a Postgres container
```console
$ docker run -d --name sentry-postgres -e POSTGRES_PASSWORD=secret -e POSTGRES_USER=sentry postgres
```
3. Generate a new secret key to be shared by all `%%REPO%%` containers. This value will then be used as the `SENTRY_SECRET_KEY` environment variable.
```console
$ docker run --rm %%IMAGE%% config generate-secret-key
```
4. If this is a new database, you'll need to run `upgrade`
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis %%IMAGE%% upgrade
```
**Note: the `-it` is important as the initial upgrade will prompt to create an initial user and will fail without it**
5. Now start up Sentry server
```console
$ docker run -d --name my-sentry -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres %%IMAGE%%
```
6. The default config needs a celery beat and celery workers, start as many workers as you need (each with a unique name)
```console
$ docker run -d --name sentry-cron -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis %%IMAGE%% run cron
$ docker run -d --name sentry-worker-1 -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-postgres:postgres --link sentry-redis:redis %%IMAGE%% run worker
```
### Port mapping
If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used. Just add `-p 8080:9000` to the `docker run` arguments and then access either `http://localhost:8080` or `http://host-ip:8080` in a browser.
## Configuring the initial user
If you did not create a superuser during `upgrade`, use the following to create one:
```console
$ docker run -it --rm -e SENTRY_SECRET_KEY='<secret-key>' --link sentry-redis:redis --link sentry-postgres:postgres %%IMAGE%% createuser
```
## Environment variables
When you start the `%%REPO%%` image, you can adjust the configuration of the Sentry instance by passing one or more environment variables on the `docker run` command line. Please note that these environment variables are provided as a jump start, and it's highly recommended to either mount in your own config file or utilize the `%%REPO%%:onbuild` variant.
### `SENTRY_SECRET_KEY`
A secret key used for cryptographic functions within Sentry. This key should be unique and consistent across all running instances. You can generate a new secret key doing something like:
```console
$ docker run --rm %%IMAGE%% config generate-secret-key
```
### `SENTRY_POSTGRES_HOST`, `SENTRY_POSTGRES_PORT`, `SENTRY_DB_NAME`, `SENTRY_DB_USER`, `SENTRY_DB_PASSWORD`
Database credentials for your Postgres server. These values aren't needed if a linked `postgres` container exists.
### `SENTRY_REDIS_HOST`, `SENTRY_REDIS_PORT`, `SENTRY_REDIS_DB`
Connection information for your Redis server. These values aren't needed if a linked `redis` container exists.
### `SENTRY_MEMCACHED_HOST`, `SENTRY_MEMCACHED_PORT`
Connection information for a Memcache server. These values aren't needed if a linked `memcached` container exists.
### `SENTRY_FILESTORE_DIR`
Directory where uploaded files will be stored. This defaults to `/var/lib/sentry/files` and is a `VOLUME` for persistent data.
### `SENTRY_SERVER_EMAIL`
The email address used for `From:` in outbound emails. Default: `root@localhost`
### `SENTRY_EMAIL_HOST`, `SENTRY_EMAIL_PORT`, `SENTRY_EMAIL_USER`, `SENTRY_EMAIL_PASSWORD`, `SENTRY_EMAIL_USE_TLS`
Connection information for an outbound smtp server. These values aren't needed if a linked `smtp` container exists.
### `SENTRY_MAILGUN_API_KEY`
If you're using Mailgun for inbound mail, set your API key and configure a route to forward to `/api/hooks/mailgun/inbound/`.

1
sentry/deprecated.md
View File

@ -1 +0,0 @@
This image is deprecated in favor of the full installation explained over at [Self-Hosted Sentry Docs](https://develop.sentry.dev/self-hosted/) (last updated July 2019; [getsentry/docker-sentry#189](https://github.com/getsentry/docker-sentry/pull/189)).

1
sentry/github-repo
View File

@ -1 +0,0 @@
https://github.com/getsentry/docker-sentry

1
sentry/license.md
View File

@ -1 +0,0 @@
View [license information](https://github.com/getsentry/sentry/blob/master/LICENSE) for the software contained in this image.

BIN
sentry/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 6.4 KiB

1
sentry/maintainer.md
View File

@ -1 +0,0 @@
[Sentry](%%GITHUB-REPO%%)

15
sentry/variant-onbuild.md
View File

@ -1,15 +0,0 @@
## `%%REPO%%:onbuild`
This image makes it easy to custom build your own Sentry instance by copying in a custom `config.yml` and/or `sentry.conf.py` file and installing plugins from `requirements.txt`.
It's also possible to develop custom extensions within your `onbuild` package. If the build directory contains a `setup.py` file, this will also get installed.
See the [official Sentry documentation](https://docs.getsentry.com/on-premise/server/installation/) for more information.
To create your custom `sentry:onbuild` package, simply do the following:
1. Create a Dockerfile containing `FROM sentry:onbuild`
2. In the same directory, add your custom configuration files.
3. You can get copies of those files to use as templates from the [docker-sentry GitHub repo](https://github.com/getsentry/docker-sentry/).
4. Build your image: `docker build -t mysentry .`
5. Run your custom image using `mysentry` instead of `sentry`.

1
sourcemage/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; lacking active maintainer

93
sourcemage/README.md
View File

@ -1,93 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "sourcemage/README.md"
IT IS AUTO-GENERATED
(from the other files in "sourcemage/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
This image is deprecated due to maintainer inactivity (last updated Dec 2016; [docker-library/official-images#2403](https://github.com/docker-library/official-images/pull/2403)).
See [docker-library/docs#1433](https://github.com/docker-library/docs/pull/1433) for discussion around an in-progress upstream update.
# Quick reference
- **Maintained by**:
[the Source Mage Community](https://github.com/vaygr/docker-sourcemage)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
- [`latest`, `0.62`](https://github.com/vaygr/docker-sourcemage/blob/a03bbe3ae7bbb839c3c69afd4504ca336f7b9cb9/stable/Dockerfile)
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/vaygr/docker-sourcemage/issues](https://github.com/vaygr/docker-sourcemage/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
[`amd64`](https://hub.docker.com/r/amd64/sourcemage/)
- **Published image artifact details**:
[repo-info repo's `repos/sourcemage/` directory](https://github.com/docker-library/repo-info/blob/master/repos/sourcemage) ([history](https://github.com/docker-library/repo-info/commits/master/repos/sourcemage))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/sourcemage` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fsourcemage)
[official-images repo's `library/sourcemage` file](https://github.com/docker-library/official-images/blob/master/library/sourcemage) ([history](https://github.com/docker-library/official-images/commits/master/library/sourcemage))
- **Source of this description**:
[docs repo's `sourcemage/` directory](https://github.com/docker-library/docs/tree/master/sourcemage) ([history](https://github.com/docker-library/docs/commits/master/sourcemage))
# Docker images for Source Mage GNU/Linux
[Source Mage](https://sourcemage.org/) (or *SMGL* in abbreviated form) is a source-based *GNU/Linux* distribution based on a sorcery metaphor of "casting" and "dispelling" programs, which we refer to as "**spells**", and a package manager called "**Sorcery**". Our packages are designed to allow the user to customize the package any way they want (custom CFLAGS, LDFLAGS, `./configure` flags, etc.) as well as offering as many of the package options as possible to the user up-front (you will not need to know what options a package has or what optional dependencies it can use ahead of time). Source code is always downloaded from the publisher's website and rarely patched. SMGL also includes many advanced features such as self-healing and sub-dependencies.
All of our scripts are [GPL](https://www.gnu.org/licenses/gpl.html)'d and our package manager and packages are written in [bash](https://www.gnu.org/software/bash/), so they are easy to learn and modify. Sorcery supports custom packages maintained by users, which can override default packages and will never be touched by updates.
![logo](https://raw.githubusercontent.com/docker-library/docs/e8be1b5dd0b212fda27669b12bedad702c184423/sourcemage/logo.png)
# Images
These images are based on our [chroot images](https://sourcemage.org/Install/Chroot). To use them, simply do the following:
```shell
$ docker run -it sourcemage
```
or
```shell
$ docker run -it sourcemage:0.62
```
---
# Notes
- in order to get the full benefit of [castfs](https://sourcemage.org/castfs) you need additional flags (`--device /dev/fuse --cap-add SYS_ADMIN`) for access to `/dev/fuse` device within a container, but you've been warned because there are security implications to granting such capabilities/privileges to the container; otherwise [installwatch](https://sourcemage.org/installwatch) will be used
- `0.62` indicates the grimoire version this image is based on, otherwise `latest` will be pulled
# License
All contents released under the [GNU Free Documentation License](https://www.gnu.org/licenses/fdl.html).
All Source Mage code released under the [GNU General Public License 2.0](https://www.gnu.org/licenses/gpl.html) or greater.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `sourcemage/` directory](https://github.com/docker-library/repo-info/tree/master/repos/sourcemage).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

28
sourcemage/content.md
View File

@ -1,28 +0,0 @@
# Docker images for Source Mage GNU/Linux
[Source Mage](https://sourcemage.org/) (or *SMGL* in abbreviated form) is a source-based *GNU/Linux* distribution based on a sorcery metaphor of "casting" and "dispelling" programs, which we refer to as "**spells**", and a package manager called "**Sorcery**". Our packages are designed to allow the user to customize the package any way they want (custom CFLAGS, LDFLAGS, `./configure` flags, etc.) as well as offering as many of the package options as possible to the user up-front (you will not need to know what options a package has or what optional dependencies it can use ahead of time). Source code is always downloaded from the publisher's website and rarely patched. SMGL also includes many advanced features such as self-healing and sub-dependencies.
All of our scripts are [GPL](https://www.gnu.org/licenses/gpl.html)'d and our package manager and packages are written in [bash](https://www.gnu.org/software/bash/), so they are easy to learn and modify. Sorcery supports custom packages maintained by users, which can override default packages and will never be touched by updates.
%%LOGO%%
# Images
These images are based on our [chroot images](https://sourcemage.org/Install/Chroot). To use them, simply do the following:
```shell
$ docker run -it %%IMAGE%%
```
or
```shell
$ docker run -it %%IMAGE%%:0.62
```
---
# Notes
- in order to get the full benefit of [castfs](https://sourcemage.org/castfs) you need additional flags (`--device /dev/fuse --cap-add SYS_ADMIN`) for access to `/dev/fuse` device within a container, but you've been warned because there are security implications to granting such capabilities/privileges to the container; otherwise [installwatch](https://sourcemage.org/installwatch) will be used
- `0.62` indicates the grimoire version this image is based on, otherwise `latest` will be pulled

3
sourcemage/deprecated.md
View File

@ -1,3 +0,0 @@
This image is deprecated due to maintainer inactivity (last updated Dec 2016; [docker-library/official-images#2403](https://github.com/docker-library/official-images/pull/2403)).
See [docker-library/docs#1433](https://github.com/docker-library/docs/pull/1433) for discussion around an in-progress upstream update.

1
sourcemage/github-repo
View File

@ -1 +0,0 @@
https://github.com/vaygr/docker-sourcemage

3
sourcemage/license.md
View File

@ -1,3 +0,0 @@
All contents released under the [GNU Free Documentation License](https://www.gnu.org/licenses/fdl.html).
All Source Mage code released under the [GNU General Public License 2.0](https://www.gnu.org/licenses/gpl.html) or greater.

BIN
sourcemage/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 21 KiB

1
sourcemage/maintainer.md
View File

@ -1 +0,0 @@
[the Source Mage Community](%%GITHUB-REPO%%)

1
swarm/README-short.txt
View File

@ -1 +0,0 @@
DEPRECATED; use "docker swarm init" instead

117
swarm/README.md
View File

@ -1,117 +0,0 @@
<!--
********************************************************************************
WARNING:
DO NOT EDIT "swarm/README.md"
IT IS AUTO-GENERATED
(from the other files in "swarm/" combined with a set of templates)
********************************************************************************
-->
# **DEPRECATION NOTICE**
> Classic Swarm has been archived and is no longer actively developed. You may want to use the Swarm mode built into the Docker Engine instead, or another orchestration system.
(https://github.com/docker/classicswarm#readme)
# Quick reference
- **Maintained by**:
[Docker, Inc.](https://github.com/docker/swarm-library-image)
- **Where to get help**:
[the Docker Community Forums](https://forums.docker.com/), [the Docker Community Slack](https://dockr.ly/slack), or [Stack Overflow](https://stackoverflow.com/search?tab=newest&q=docker)
# Supported tags and respective `Dockerfile` links
**No supported tags**
# Quick reference (cont.)
- **Where to file issues**:
[https://github.com/docker/swarm-library-image/issues](https://github.com/docker/swarm-library-image/issues)
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
**No supported architectures**
- **Published image artifact details**:
[repo-info repo's `repos/swarm/` directory](https://github.com/docker-library/repo-info/blob/master/repos/swarm) ([history](https://github.com/docker-library/repo-info/commits/master/repos/swarm))
(image metadata, transfer size, etc)
- **Image updates**:
[official-images repo's `library/swarm` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2Fswarm)
[official-images repo's `library/swarm` file](https://github.com/docker-library/official-images/blob/master/library/swarm) ([history](https://github.com/docker-library/official-images/commits/master/library/swarm))
- **Source of this description**:
[docs repo's `swarm/` directory](https://github.com/docker-library/docs/tree/master/swarm) ([history](https://github.com/docker-library/docs/commits/master/swarm))
# Swarm: a Docker-native clustering system
![logo](https://raw.githubusercontent.com/docker-library/docs/471fa6e4cb58062ccbf91afc111980f9c7004981/swarm/logo.png)
`swarm` is a simple tool which controls a cluster of Docker hosts and exposes it as a single "virtual" host.
`swarm` uses the standard Docker API as its frontend, which means any tool which speaks Docker can control swarm transparently: dokku, docker-compose, krane, flynn, deis, docker-ui, shipyard, drone.io, Jenkins... and of course the Docker client itself.
Like the other Docker projects, `swarm` follows the "batteries included but removable" principle. It ships with a simple scheduling backend out of the box, and as initial development settles, an API will develop to enable pluggable backends. The goal is to provide a smooth out-of-box experience for simple use cases, and allow swapping in more powerful backends, like `Mesos`, for large scale production deployments.
# Example usage
```bash
# create a cluster
$ docker run --rm swarm create
6856663cdefdec325839a4b7e1de38e8 # <- this is your unique <cluster_id>
# on each of your nodes, start the swarm agent
# <node_ip> doesn't have to be public (eg. 192.168.0.X),
# as long as the swarm manager can access it.
$ docker run -d swarm join --addr=<node_ip:2375> token://<cluster_id>
# start the manager on any machine or your laptop
$ docker run -t -p <swarm_port>:2375 -t swarm manage token://<cluster_id>
# use the regular docker cli
$ docker -H tcp://<swarm_ip:swarm_port> info
$ docker -H tcp://<swarm_ip:swarm_port> run ...
$ docker -H tcp://<swarm_ip:swarm_port> ps
$ docker -H tcp://<swarm_ip:swarm_port> logs ...
...
# list nodes in your cluster
$ docker run --rm swarm list token://<cluster_id>
<node_ip:2375>
```
See [here](https://github.com/docker/swarm/blob/master/discovery/README.md) for more information about other discovery services.
## Advanced Scheduling
See [filters](https://github.com/docker/swarm/blob/master/scheduler/filter/README.md) and [strategies](https://github.com/docker/swarm/blob/master/scheduler/strategy/README.md) to learn more about advanced scheduling.
## TLS
Swarm supports TLS authentication between the CLI and Swarm but also between Swarm and the Docker nodes.
In order to enable TLS, the same command line options as Docker can be specified:
`swarm manage --tlsverify --tlscacert=<CACERT> --tlscert=<CERT> --tlskey=<KEY> [...]`
Please refer to the [Docker documentation](https://docs.docker.com/articles/https/) for more information on how to set up TLS authentication on Docker and generating the certificates.
Note that Swarm certificates must be generated with `extendedKeyUsage = clientAuth,serverAuth`.
# License
View [license information](https://github.com/docker/swarm/blob/master/LICENSE.code) for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in [the `repo-info` repository's `swarm/` directory](https://github.com/docker-library/repo-info/tree/master/repos/swarm).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

54
swarm/content.md
View File

@ -1,54 +0,0 @@
# Swarm: a Docker-native clustering system
%%LOGO%%
`swarm` is a simple tool which controls a cluster of Docker hosts and exposes it as a single "virtual" host.
`swarm` uses the standard Docker API as its frontend, which means any tool which speaks Docker can control swarm transparently: dokku, docker-compose, krane, flynn, deis, docker-ui, shipyard, drone.io, Jenkins... and of course the Docker client itself.
Like the other Docker projects, `swarm` follows the "batteries included but removable" principle. It ships with a simple scheduling backend out of the box, and as initial development settles, an API will develop to enable pluggable backends. The goal is to provide a smooth out-of-box experience for simple use cases, and allow swapping in more powerful backends, like `Mesos`, for large scale production deployments.
# Example usage
```bash
# create a cluster
$ docker run --rm %%IMAGE%% create
6856663cdefdec325839a4b7e1de38e8 # <- this is your unique <cluster_id>
# on each of your nodes, start the swarm agent
# <node_ip> doesn't have to be public (eg. 192.168.0.X),
# as long as the swarm manager can access it.
$ docker run -d %%IMAGE%% join --addr=<node_ip:2375> token://<cluster_id>
# start the manager on any machine or your laptop
$ docker run -t -p <swarm_port>:2375 -t %%IMAGE%% manage token://<cluster_id>
# use the regular docker cli
$ docker -H tcp://<swarm_ip:swarm_port> info
$ docker -H tcp://<swarm_ip:swarm_port> run ...
$ docker -H tcp://<swarm_ip:swarm_port> ps
$ docker -H tcp://<swarm_ip:swarm_port> logs ...
...
# list nodes in your cluster
$ docker run --rm %%IMAGE%% list token://<cluster_id>
<node_ip:2375>
```
See [here](https://github.com/docker/swarm/blob/master/discovery/README.md) for more information about other discovery services.
## Advanced Scheduling
See [filters](https://github.com/docker/swarm/blob/master/scheduler/filter/README.md) and [strategies](https://github.com/docker/swarm/blob/master/scheduler/strategy/README.md) to learn more about advanced scheduling.
## TLS
Swarm supports TLS authentication between the CLI and Swarm but also between Swarm and the Docker nodes.
In order to enable TLS, the same command line options as Docker can be specified:
`swarm manage --tlsverify --tlscacert=<CACERT> --tlscert=<CERT> --tlskey=<KEY> [...]`
Please refer to the [Docker documentation](https://docs.docker.com/articles/https/) for more information on how to set up TLS authentication on Docker and generating the certificates.
Note that Swarm certificates must be generated with `extendedKeyUsage = clientAuth,serverAuth`.

3
swarm/deprecated.md
View File

@ -1,3 +0,0 @@
> Classic Swarm has been archived and is no longer actively developed. You may want to use the Swarm mode built into the Docker Engine instead, or another orchestration system.
(https://github.com/docker/classicswarm#readme)

1
swarm/github-repo
View File

@ -1 +0,0 @@
https://github.com/docker/swarm-library-image

1
swarm/license.md
View File

@ -1 +0,0 @@
View [license information](https://github.com/docker/swarm/blob/master/LICENSE.code) for the software contained in this image.

BIN
swarm/logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 121 KiB

1
swarm/maintainer.md
View File

@ -1 +0,0 @@
../.common-templates/maintainer-docker.md

Some files were not shown because too many files have changed in this diff Show More