This is page 18 of 25. Use http://codebase.md/id/docs/get_started/create/basic_markup.html?lines=true&page={x} to view the full context.
# Directory Structure
```
├── .ci
│ ├── check-markdownfmt.sh
│ ├── check-metadata.sh
│ ├── check-pr-no-readme.sh
│ ├── check-required-files.sh
│ ├── check-short.sh
│ ├── check-ymlfmt.sh
│ └── get-markdownfmt.sh
├── .common-templates
│ ├── maintainer-community.md
│ ├── maintainer-docker.md
│ ├── maintainer-hashicorp.md
│ └── maintainer-influxdata.md
├── .dockerignore
├── .github
│ └── workflows
│ └── ci.yml
├── .template-helpers
│ ├── arches.sh
│ ├── autogenerated-warning.md
│ ├── compose.md
│ ├── generate-dockerfile-links-partial.sh
│ ├── generate-dockerfile-links-partial.tmpl
│ ├── get-help.md
│ ├── issues.md
│ ├── license-common.md
│ ├── template.md
│ ├── variant-alpine.md
│ ├── variant-default-buildpack-deps.md
│ ├── variant-default-debian.md
│ ├── variant-default-ubuntu.md
│ ├── variant-onbuild.md
│ ├── variant-slim.md
│ ├── variant-windowsservercore.md
│ ├── variant.md
│ └── variant.sh
├── adminer
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── aerospike
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── almalinux
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── alpine
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── alt
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── amazoncorretto
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── amazonlinux
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── api-firewall
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── arangodb
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── archlinux
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── backdrop
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── bash
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── bonita
│ ├── compose.yaml
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── buildpack-deps
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── busybox
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-glibc.md
│ ├── variant-musl.md
│ ├── variant-uclibc.md
│ └── variant.md
├── caddy
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo-120.png
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── cassandra
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── chronograf
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── cirros
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── clearlinux
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── clefos
│ ├── content.md
│ ├── deprecated.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── clickhouse
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── clojure
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── composer
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── convertigo
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── couchbase
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── couchdb
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── crate
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── dart
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── debian
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-slim.md
│ └── variant.md
├── docker
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-rootless.md
│ └── variant-windowsservercore.md
├── Dockerfile
├── drupal
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-fpm.md
├── eclipse-mosquitto
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── eclipse-temurin
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── eggdrop
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── elasticsearch
│ ├── compose.yaml
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-alpine.md
├── elixir
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── emqx
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── erlang
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── fedora
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── flink
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── fluentd
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── friendica
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── gazebo
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── gcc
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── generate-repo-stub-readme.sh
├── geonetwork
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-postgres.md
│ └── variant.md
├── get-categories.sh
├── ghost
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── golang
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-alpine.md
│ └── variant-tip.md
├── gradle
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── groovy
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── haproxy
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── haskell
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-slim.md
├── haxe
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── hello-world
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── update.sh
├── hitch
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── httpd
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── hylang
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── ibm-semeru-runtimes
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── ibmjava
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── influxdb
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-data.md
│ └── variant-meta.md
├── irssi
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── jetty
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── joomla
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── jruby
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── julia
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── kapacitor
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── kibana
│ ├── compose.yaml
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── kong
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── krakend
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo-120.png
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── LICENSE
├── lightstreamer
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── liquibase
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── logstash
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-alpine.md
├── mageia
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── mariadb
│ ├── compose.yaml
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── markdownfmt.sh
├── matomo
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── maven
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── mediawiki
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── memcached
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── metadata.json
├── metadata.sh
├── mongo
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── mongo-express
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── monica
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── mono
│ ├── content.md
│ ├── deprecated.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── mysql
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── nats
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── neo4j
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── neurodebian
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── nextcloud
│ ├── content.md
│ ├── deprecated.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── nginx
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-perl.md
├── node
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── notary
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── odoo
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── open-liberty
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── openjdk
│ ├── content.md
│ ├── deprecated.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-alpine.md
│ ├── variant-oracle.md
│ └── variant-slim.md
├── oraclelinux
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-slim.md
├── orientdb
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── parallel-update.sh
├── percona
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── perl
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── photon
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── php
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-apache.md
│ ├── variant-cli.md
│ ├── variant-fpm.md
│ └── variant.md
├── php-zendserver
│ ├── content.md
│ ├── deprecated.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── phpmyadmin
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── plone
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── postfixadmin
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-apache.md
│ ├── variant-fpm-alpine.md
│ └── variant-fpm.md
├── postgres
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── push.pl
├── push.sh
├── pypy
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── python
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-slim.md
├── r-base
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rabbitmq
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rakudo-star
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── README.md
├── redis
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── redmine
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── registry
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rethinkdb
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rocket.chat
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rockylinux
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── ros
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── ruby
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── rust
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── sapmachine
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── satosa
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── scratch
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── silverpeas
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── solr
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── sonarqube
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── spark
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── spiped
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── storm
│ ├── compose.yaml
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── swift
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── swipl
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── teamspeak
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── telegraf
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── tomcat
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── tomee
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── traefik
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-alpine.md
├── ubuntu
│ ├── content.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── unit
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── update.sh
├── varnish
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── websphere-liberty
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── wordpress
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ ├── variant-cli.md
│ └── variant-fpm.md
├── xwiki
│ ├── content.md
│ ├── get-help.md
│ ├── github-repo
│ ├── issues.md
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ └── README.md
├── ymlfmt.sh
├── yourls
│ ├── compose.yaml
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.svg
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-fpm.md
├── znc
│ ├── content.md
│ ├── github-repo
│ ├── license.md
│ ├── logo.png
│ ├── maintainer.md
│ ├── metadata.json
│ ├── README-short.txt
│ ├── README.md
│ └── variant-slim.md
└── zookeeper
├── compose.yaml
├── content.md
├── github-repo
├── license.md
├── logo.png
├── maintainer.md
├── metadata.json
├── README-short.txt
└── README.md
```
# Files
--------------------------------------------------------------------------------
/groovy/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Groovy?
2 |
3 | [Apache Groovy](http://groovy-lang.org/) is a powerful, optionally typed and dynamic language, with static-typing and static compilation capabilities, for the Java platform aimed at improving developer productivity thanks to a concise, familiar and easy to learn syntax. It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain-Specific Language authoring, runtime and compile-time meta-programming and functional programming.
4 |
5 | %%LOGO%%
6 |
7 | # How to use this image
8 |
9 | Note that if you are mounting a volume and the uid running Docker is not `1000`, you should run as user `root` (`-u root`).
10 |
11 | ## Starting Groovysh
12 |
13 | `docker run -it --rm groovy`
14 |
15 | ## Running a Groovy script
16 |
17 | `docker run --rm -v "$PWD":/home/groovy/scripts -w /home/groovy/scripts %%IMAGE%% groovy <script> <script-args>`
18 |
19 | ## Reusing the Grapes cache
20 |
21 | The local Grapes cache can be reused across containers by creating a volume and mounting it in `/home/groovy/.groovy/grapes`.
22 |
23 | ```console
24 | docker volume create --name grapes-cache
25 | docker run --rm -it -v grapes-cache:/home/groovy/.groovy/grapes %%IMAGE%%
26 | ```
27 |
```
--------------------------------------------------------------------------------
/.template-helpers/variant-alpine.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:<version>-alpine`
2 |
3 | This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
4 |
5 | This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use [musl libc](https://musl.libc.org) instead of [glibc and friends](https://www.etalabs.net/compare_libcs.html), so software will often run into issues depending on the depth of their libc requirements/assumptions. See [this Hacker News comment thread](https://news.ycombinator.com/item?id=10782897) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
6 |
7 | To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
8 |
```
--------------------------------------------------------------------------------
/sapmachine/content.md:
--------------------------------------------------------------------------------
```markdown
1 | ### Overview
2 |
3 | SapMachine is a binary distribution of the [Open Java Development Kit (OpenJDK)](https://openjdk.org/). It is built, quality tested and long-term supported by SAP.
4 |
5 | SapMachine is the default Java runtime for [SAP's Business Technology Platform](https://www.sap.com/products/technology-platform.html) and it is also supported as a [Standard JRE](https://github.com/cloudfoundry/java-buildpack/blob/master/docs/jre-sap_machine_jre.md) in the [Cloud Foundry Java Build Pack](https://github.com/cloudfoundry/java-buildpack).
6 |
7 | For more information see the [SapMachine website](https://sapmachine.io).
8 |
9 | Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
10 |
11 | %%LOGO%%
12 |
13 | ### How to use this Image
14 |
15 | You can pull and test the image with the following commands:
16 |
17 | ```console
18 | docker pull %%IMAGE%%:latest
19 | docker run -it %%IMAGE%%:latest java -version
20 | ```
21 |
22 | You can also use the SapMachine image as a base image to run your own jar file:
23 |
24 | ```dockerfile
25 | FROM %%IMAGE%%:latest
26 | RUN mkdir /opt/myapp
27 | COPY myapp.jar /opt/myapp
28 | CMD ["java", "-jar", "/opt/myapp/myapp.jar"]
29 | ```
30 |
31 | You can then build and run your own Docker image:
32 |
33 | ```console
34 | docker build -t myapp .
35 | docker run -it --rm myapp
36 | ```
37 |
```
--------------------------------------------------------------------------------
/elixir/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Elixir?
2 |
3 | Elixir is a dynamic, functional language designed for building scalable and maintainable applications.
4 |
5 | Elixir leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems, while also being successfully used in web development and the embedded software domain.
6 |
7 | > [en.wikipedia.org/wiki/Elixir_(programming_language)](https://en.wikipedia.org/wiki/Elixir_%28programming_language%29)
8 |
9 | %%LOGO%%
10 |
11 | # How to use this image
12 |
13 | ## Run it as the REPL
14 |
15 | ```console
16 | ➸ docker run -it --rm %%IMAGE%%
17 | Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
18 |
19 | Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
20 | iex(1)> System.version
21 | "1.2.1"
22 | iex(2)>
23 | ➸ docker run -it --rm -h elixir.local %%IMAGE%% iex --sname snode
24 | Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
25 |
26 | Interactive Elixir (1.2.1) - press Ctrl+C to exit (type h() ENTER for help)
27 | iex(snode@elixir)1> System.version
28 | "1.2.1"
29 | iex(snode@elixir)2> :c.uptime
30 | 14 seconds
31 | :ok
32 | ```
33 |
34 | ## Run a single Elixir exs script
35 |
36 | ```console
37 | $ docker run -it --rm --name %%REPO%%-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%% elixir your-escript.exs
38 | ```
39 |
```
--------------------------------------------------------------------------------
/xwiki/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is XWiki
2 |
3 | [XWiki](http://xwiki.org) is a free wiki software platform written in Java with a design emphasis on extensibility. XWiki is an enterprise wiki. It includes WYSIWYG editing, OpenDocument based document import/export, semantic annotations and tagging, and advanced permissions management.
4 |
5 | As an application wiki, XWiki allows for the storing of structured data and the execution of server side script within the wiki interface. Scripting languages including Velocity, Groovy, Python, Ruby and PHP can be written directly into wiki pages using wiki macros. User-created data structures can be defined in wiki documents and instances of those structures can be attached to wiki documents, stored in a database, and queried using either Hibernate query language or XWiki's own query language.
6 |
7 | [XWiki.org's extension wiki](http://extensions.xwiki.org) is home to XWiki extensions ranging from [code snippets](http://snippets.xwiki.org) which can be pasted into wiki pages to loadable core modules. Many of XWiki Enterprise's features are provided by extensions which are bundled with it.
8 |
9 | %%LOGO%%
10 |
11 | # Usage
12 |
13 | Please check the [documentation](https://github.com/xwiki-contrib/docker-xwiki/blob/master/README.md) to learn how to use the XWiki Docker images.
14 |
```
--------------------------------------------------------------------------------
/znc/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is ZNC?
2 |
3 | ZNC is an IRC network bouncer (BNC). It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same nickname on IRC.
4 |
5 | %%LOGO%%
6 |
7 | [ZNC Wiki](http://znc.in/)
8 |
9 | # How to use this image
10 |
11 | ZNC in this image stores its configuration in `/znc-data`. If you have existing configuration, you can reuse it with `-v $HOME/.znc:/znc-data`. Alternatively, you can create a new config in a volume or in a local dir. The examples below assumes a volume named `znc-cfg`.
12 |
13 | ```console
14 | $ docker run -it -v znc-cfg:/znc-data %%IMAGE%% --makeconf
15 | ```
16 |
17 | To run ZNC:
18 |
19 | ```console
20 | $ docker run -p 12345:12345 -v znc-cfg:/znc-data %%IMAGE%%
21 | ```
22 |
23 | The port (12345 in the example above) should match the port you used during `--makeconf`. Note that 6667 and 6697 are often blocked by web browsers, and therefore are not recommended for ZNC.
24 |
25 | If you use any external module, put the .cpp, .py or .pm file to `/znc-data/modules` (you may need to create that directory).
26 |
27 | This image contains the latest released version. If you want the bleeding edge (unstable) version, it's at [zncbouncer/znc-git](https://hub.docker.com/r/zncbouncer/znc-git).
28 |
```
--------------------------------------------------------------------------------
/.template-helpers/template.md:
--------------------------------------------------------------------------------
```markdown
1 | # Quick reference
2 |
3 | - **Maintained by**:
4 | %%MAINTAINER%%
5 |
6 | - **Where to get help**:
7 | %%GET-HELP%%
8 |
9 | # Supported tags and respective `Dockerfile` links
10 |
11 | %%TAGS%%
12 |
13 | # Quick reference (cont.)
14 |
15 | - **Where to file issues**:
16 | %%ISSUES%%
17 |
18 | - **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
19 | %%ARCHES%%
20 |
21 | - **Published image artifact details**:
22 | [repo-info repo's `repos/%%REPO%%/` directory](https://github.com/docker-library/repo-info/blob/master/repos/%%REPO%%) ([history](https://github.com/docker-library/repo-info/commits/master/repos/%%REPO%%))
23 | (image metadata, transfer size, etc)
24 |
25 | - **Image updates**:
26 | [official-images repo's `library/%%REPO%%` label](https://github.com/docker-library/official-images/issues?q=label%3Alibrary%2F%%REPO%%)
27 | [official-images repo's `library/%%REPO%%` file](https://github.com/docker-library/official-images/blob/master/library/%%REPO%%) ([history](https://github.com/docker-library/official-images/commits/master/library/%%REPO%%))
28 |
29 | - **Source of this description**:
30 | [docs repo's `%%REPO%%/` directory](https://github.com/docker-library/docs/tree/master/%%REPO%%) ([history](https://github.com/docker-library/docs/commits/master/%%REPO%%))
31 |
32 | %%CONTENT%%%%VARIANT%%%%LICENSE%%
33 |
```
--------------------------------------------------------------------------------
/mageia/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Mageia?
2 |
3 | [Mageia](http://www.mageia.org) is a GNU/Linux-based, Free Software operating system. It is a [community](https://www.mageia.org/en/community/) project, supported by [a non-profit organisation](https://www.mageia.org/en/about/#mageia.org) of elected contributors.
4 |
5 | %%LOGO%%
6 |
7 | Our mission: to build great tools for people.
8 |
9 | Further than just delivering a secure, stable and sustainable operating system, the goal is to set up a stable and trustable governance to direct collaborative projects.
10 |
11 | To date, Mageia:
12 |
13 | - [started in September 2010 as a fork](https://www.mageia.org/en/about/2010-sept-announcement.html) of Mandriva Linux;
14 | - gathered hundreds of careful individuals and several companies worldwide,who coproduce the infrastructure, the distribution itself, [documentation](https://wiki.mageia.org/), [delivery](https://www.mageia.org/en/downloads/) and [support](https://www.mageia.org/en/support/), using Free Software tools;
15 | - released major stable releases every year since 2011
16 |
17 | # How to use this image
18 |
19 | ## Create a Dockerfile for your container
20 |
21 | ```dockerfile
22 | FROM %%IMAGE%%:6
23 | MAINTAINER "Foo Bar" <[email protected]>
24 | CMD [ "bash" ]
25 | ```
26 |
27 | ## Installed packages
28 |
29 | The images include the following packages:
30 |
31 | - basesystem-minimal
32 | - dnf (Mageia 6+)
33 | - locales
34 | - locales-en
35 | - urpmi
36 |
```
--------------------------------------------------------------------------------
/hylang/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Hy?
2 |
3 | Hy (a.k.a., Hylang) is a dialect of the Lisp programming language designed to interoperate with Python by translating expressions into Python's abstract syntax tree (AST). Similar to Clojure's mapping of s-expressions onto the JVM, Hy is meant to operate as a transparent Lisp front end to Python's abstract syntax. Hy also allows for Python libraries (including the standard library) to be imported and accessed alongside Hy code with a compilation step, converting the data structure of both into Python's AST.
4 |
5 | > [wikipedia.org/wiki/Hy](https://en.wikipedia.org/wiki/Hy)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Create a `Dockerfile` in your Hy project
12 |
13 | ```dockerfile
14 | FROM %%IMAGE%%:0.10
15 | COPY . /usr/src/myapp
16 | WORKDIR /usr/src/myapp
17 | CMD [ "hy", "./your-daemon-or-script.hy" ]
18 | ```
19 |
20 | You can then build and run the Docker image:
21 |
22 | ```console
23 | $ docker build -t my-hylang-app
24 | $ docker run -it --rm --name my-running-app my-hylang-app
25 | ```
26 |
27 | ## Run a single Hy script
28 |
29 | For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Hy script by using the Hy Docker image directly:
30 |
31 | ```console
32 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:0.10 hy your-daemon-or-script.hy
33 | ```
34 |
```
--------------------------------------------------------------------------------
/drupal/logo.svg:
--------------------------------------------------------------------------------
```
1 | <svg xmlns="http://www.w3.org/2000/svg" width="186.52541" height="243.71308" viewBox="0 0 186.52541 243.71308"><title>Risorsa 85</title><g id="Livello_2" data-name="Livello 2"><g id="Livello_1-2" data-name="Livello 1"><path d="M131.64024,51.90954C114.49124,34.76866,98.12945,18.42858,93.26,0,88.39024,18.42858,72.02583,34.76866,54.8797,51.90954,29.16037,77.61263,0,106.7432,0,150.434a93.26271,93.26271,0,1,0,186.52541,0c0-43.688-29.158-72.8214-54.88517-98.52449M39.63956,172.16578c-5.71847-.19418-26.82308-36.57089,12.32937-75.303l25.90873,28.30088a2.21467,2.21467,0,0,1-.173,3.30485c-6.18245,6.34085-32.53369,32.7658-35.809,41.90292-.676,1.886-1.66339,1.81463-2.25619,1.79436M93.26283,220.1092a32.07521,32.07521,0,0,1-32.07544-32.07543A33.42322,33.42322,0,0,1,69.1821,166.8471c5.7836-7.07224,24.07643-26.96358,24.07643-26.96358s18.01279,20.18332,24.03326,26.89607a31.36794,31.36794,0,0,1,8.04647,21.25418A32.07551,32.07551,0,0,1,93.26283,220.1092m61.3923-52.015c-.69131,1.51192-2.25954,4.036-4.37617,4.113-3.77288.13741-4.176-1.79579-6.96465-5.92291-6.12235-9.06007-59.55167-64.89991-69.54517-75.69925-8.79026-9.49851-1.23783-16.195,2.26549-19.70431C80.42989,66.47768,93.25949,53.656,93.25949,53.656s38.25479,36.29607,54.19029,61.09626,10.44364,46.26024,7.20535,53.342" style="fill:#009cde"/></g></g></svg>
```
--------------------------------------------------------------------------------
/.template-helpers/variant-onbuild.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:<version>-onbuild`
2 |
3 | The `ONBUILD` image variants are deprecated, and their usage is discouraged. For more details, see [docker-library/official-images#2076](https://github.com/docker-library/official-images/issues/2076).
4 |
5 | While the `onbuild` variant is really useful for "getting off the ground running" (zero to Dockerized in a short period of time), it's not recommended for long-term usage within a project due to the lack of control over *when* the `ONBUILD` triggers fire (see also [`docker/docker#5714`](https://github.com/docker/docker/issues/5714), [`docker/docker#8240`](https://github.com/docker/docker/issues/8240), [`docker/docker#11917`](https://github.com/docker/docker/issues/11917)).
6 |
7 | Once you've got a handle on how your project functions within Docker, you'll probably want to adjust your `Dockerfile` to inherit from a non-`onbuild` variant and copy the commands from the `onbuild` variant `Dockerfile` (moving the `ONBUILD` lines to the end and removing the `ONBUILD` keywords) into your own file so that you have tighter control over them and more transparency for yourself and others looking at your `Dockerfile` as to what it does. This also makes it easier to add additional requirements as time goes on (such as installing more packages before performing the previously-`ONBUILD` steps).
8 |
```
--------------------------------------------------------------------------------
/golang/variant-alpine.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:<version>-alpine`
2 |
3 | This image is based on the popular [Alpine Linux project](https://alpinelinux.org), available in [the `alpine` official image](https://hub.docker.com/_/alpine). Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
4 |
5 | This variant is highly experimental, and *not* officially supported by the Go project (see [golang/go#19938](https://github.com/golang/go/issues/19938) for details).
6 |
7 | The main caveat to note is that it does use [musl libc](https://musl.libc.org) instead of [glibc and friends](https://www.etalabs.net/compare_libcs.html), which can lead to unexpected behavior. See [this Hacker News comment thread](https://news.ycombinator.com/item?id=10782897) for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
8 |
9 | To minimize image size, additional related tools (such as `git`, `gcc`, or `bash`) are not included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar). See also [docker-library/golang#250 (comment)](https://github.com/docker-library/golang/issues/250#issuecomment-451201761) for a longer explanation.
10 |
```
--------------------------------------------------------------------------------
/julia/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Julia?
2 |
3 | Julia is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical computing environments. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library.
4 |
5 | > [julialang.org](http://julialang.org/)
6 |
7 | %%LOGO%%
8 |
9 | # Support Tiers
10 |
11 | Platforms supported by Julia are divided into a tier system that ranks them based on level of support. For more dedicated information about support tiers, please see ["Currently supported platforms" on the Julia download page](https://julialang.org/downloads/#currently_supported_platforms).
12 |
13 | It's especially relevant to note that Alpine / musl is "Tier 3" due to several known issues (see [docker-library/julia#47 (comment)](https://github.com/docker-library/julia/pull/47#issuecomment-652661869), [JuliaLang/julia#28805](https://github.com/JuliaLang/julia/issues/28805), [JuliaLang/julia#36458](https://github.com/JuliaLang/julia/issues/36458)).
14 |
15 | # How to use this image
16 |
17 | ## Start Julia REPL
18 |
19 | Starting the Julia REPL is as easy as the following:
20 |
21 | ```console
22 | $ docker run -it --rm %%IMAGE%%
23 | ```
24 |
25 | ## Run Julia script from your local directory inside container
26 |
27 | ```console
28 | $ docker run -it --rm -v "$PWD":/usr/myapp -w /usr/myapp %%IMAGE%% julia script.jl arg1 arg2
29 | ```
30 |
```
--------------------------------------------------------------------------------
/memcached/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Memcached?
2 |
3 | Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.
4 |
5 | Memcached's APIs provide a very large hash table distributed across multiple machines. When the table is full, subsequent inserts cause older data to be purged in least recently used order. Applications using Memcached typically layer requests and additions into RAM before falling back on a slower backing store, such as a database.
6 |
7 | > [wikipedia.org/wiki/Memcached](https://en.wikipedia.org/wiki/Memcached)
8 |
9 | # How to use this image
10 |
11 | ```console
12 | $ docker run --name my-memcache -d %%IMAGE%%
13 | ```
14 |
15 | ### Configuration
16 |
17 | To customize the configuration of the memcached server, first obtain the upstream configuration options from the container:
18 |
19 | ```console
20 | $ docker run --rm %%IMAGE%% -h
21 | ```
22 |
23 | Using `docker run`:
24 |
25 | ```console
26 | $ docker run --name my-memcache -d %%IMAGE%% memcached --memory-limit=64
27 | ```
28 |
29 | or using Docker Compose:
30 |
31 | ```yaml
32 | services:
33 | memcached:
34 | image: %%IMAGE%%
35 | command:
36 | - --conn-limit=1024
37 | - --memory-limit=64
38 | - --threads=4
39 | ```
40 |
41 | For infomation on configuring your memcached server, see the extensive [wiki](https://github.com/memcached/memcached/wiki).
42 |
```
--------------------------------------------------------------------------------
/neurodebian/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is NeuroDebian?
2 |
3 | NeuroDebian provides a large collection of popular neuroscience research software for the [Debian](http://www.debian.org) operating system as well as [Ubuntu](http://www.ubuntu.com) and other derivatives. Popular packages include*AFNI*, *FSL*, *PyMVPA*, and many others. While we do strive to maintain a high level of quality, we make no guarantee that a given package works as expected, so use them at your own risk.
4 |
5 | > [neuro.debian.net](http://neuro.debian.net/)
6 |
7 | %%LOGO%%
8 |
9 | # About this image
10 |
11 | NeuroDebian images only add NeuroDebian repository and repository's GPG key. No apt indexes are downloaded, so `apt-get update` needs to be ran before any use of `apt-get`.
12 |
13 | `nd` tags are used to reflect suffixes used in versions of packages available from NeuroDebian.
14 |
15 | The `%%IMAGE%%:latest` tag will always point the Neurodebian-enabled latest stable release of Debian (which is, at the time of this writing, `debian:wheezy`).
16 |
17 | ## sources.list
18 |
19 | NeuroDebian APT file is installed under `/etc/apt/sources.list.d/neurodebian.sources.list` and currently enables only `main` (DFSG-compliant) area of the archive:
20 |
21 | ```console
22 | $ docker run %%IMAGE%% cat /etc/apt/sources.list.d/neurodebian.sources.list
23 | deb http://neuro.debian.net/debian wheezy main
24 | deb http://neuro.debian.net/debian data main
25 | #deb-src http://neuro.debian.net/debian-devel wheezy main
26 | ```
27 |
```
--------------------------------------------------------------------------------
/gradle/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Gradle?
2 |
3 | [Gradle](https://gradle.org/) is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites. Gradle has been designed to support build automation across multiple languages and platforms including Java, Scala, Android, C/C++, and Groovy, and is closely integrated with development tools and continuous integration servers including Eclipse, IntelliJ, and Jenkins.
4 |
5 | %%LOGO%%
6 |
7 | # How to use this image
8 |
9 | ## Building a Gradle project
10 |
11 | Run this from the directory of the Gradle project you want to build.
12 |
13 | `docker run --rm -u gradle -v "$PWD":/home/gradle/project -w /home/gradle/project %%IMAGE%% gradle <gradle-task>`
14 |
15 | Note the above command runs using uid/gid 1000 (user *gradle*) to avoid running as root.
16 |
17 | If you are mounting a volume and the uid/gid running Docker is not *1000*, you should run as user *root* (`-u root`). *root* is also the default, so you can also simply not specify a user.
18 |
19 | ## Java 21 support
20 |
21 | Java 21 does not currently support build customizations using Kotlin (such as using the `kotlin-dsl` plugin in a buildSrc script). Full support for Java 21 will come in a future Gradle release.
22 |
```
--------------------------------------------------------------------------------
/irssi/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is irssi?
2 |
3 | Irssi is a terminal based IRC client for UNIX systems. It also supports SILC and ICB protocols via plugins. Some people refer to it as 'the client of the future'.
4 |
5 | > [irssi.org](http://irssi.org)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | Because it is unlikely any two irssi users have the same configuration preferences, this image does not include an irssi configuration. To configure irssi to your liking, please refer to [upstream's excellent (and comprehensive) +documentation](http://irssi.org/documentation).
12 |
13 | Be sure to also checkout the [awesome scripts](https://github.com/irssi/scripts.irssi.org) you can download to customize your irssi configuration.
14 |
15 | ## Directly via bind mount
16 |
17 | On a Linux system, build and launch a container named `my-running-irssi` like this:
18 |
19 | ```console
20 | $ docker run -it --name my-running-irssi -e TERM -u $(id -u):$(id -g) \
21 | --log-driver=none \
22 | -v $HOME/.irssi:/home/user/.irssi:ro \
23 | -v /etc/localtime:/etc/localtime:ro \
24 | %%IMAGE%%
25 | ```
26 |
27 | We specify `--log-driver=none` to avoid storing useless interactive terminal data.
28 |
29 | On a Mac OS X system, run the same image using:
30 |
31 | ```console
32 | $ docker run -it --name my-running-irssi -e TERM -u $(id -u):$(id -g) \
33 | --log-driver=none \
34 | -v $HOME/.irssi:/home/user/.irssi:ro \
35 | %%IMAGE%%
36 | ```
37 |
38 | You omit `/etc/localtime` on Mac OS X because `boot2docker` doesn't use this file.
39 |
```
--------------------------------------------------------------------------------
/php/variant-apache.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:<version>-apache`
2 |
3 | This image contains Debian's Apache httpd in conjunction with PHP (as `mod_php`) and uses `mpm_prefork` by default.
4 |
5 | ### Apache with a `Dockerfile`
6 |
7 | ```dockerfile
8 | FROM %%IMAGE%%:7.2-apache
9 | COPY src/ /var/www/html/
10 | ```
11 |
12 | Where `src/` is the directory containing all your PHP code. Then, run the commands to build and run the Docker image:
13 |
14 | ```console
15 | $ docker build -t my-php-app .
16 | $ docker run -d --name my-running-app my-php-app
17 | ```
18 |
19 | We recommend that you add a `php.ini` configuration file; see the "Configuration" section for details.
20 |
21 | ### Apache without a `Dockerfile`
22 |
23 | ```console
24 | $ docker run -d -p 80:80 --name my-apache-php-app -v "$PWD":/var/www/html %%IMAGE%%:7.2-apache
25 | ```
26 |
27 | ### Changing `DocumentRoot` (or other Apache configuration)
28 |
29 | Some applications may wish to change the default `DocumentRoot` in Apache (away from `/var/www/html`). The following demonstrates one way to do so using an environment variable (which can then be modified at container runtime as well):
30 |
31 | ```dockerfile
32 | FROM %%IMAGE%%:7.1-apache
33 |
34 | ENV APACHE_DOCUMENT_ROOT /path/to/new/root
35 |
36 | RUN sed -ri -e 's!/var/www/html!${APACHE_DOCUMENT_ROOT}!g' /etc/apache2/sites-available/*.conf
37 | RUN sed -ri -e 's!/var/www/!${APACHE_DOCUMENT_ROOT}!g' /etc/apache2/apache2.conf /etc/apache2/conf-available/*.conf
38 | ```
39 |
40 | A similar technique could be employed for other Apache configuration options.
41 |
```
--------------------------------------------------------------------------------
/liquibase/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Liquibase?
2 |
3 | Liquibase is DevOps for your database. More information about Liquibase can be found at [http://www.liquibase.org](http://www.liquibase.org).
4 |
5 | Liquibase compares the contents of a Change Log to the database to determine which, if any, changes need to be applied to the database. For example, you can create tables, add columns, and many more with Liquibase. Liquibase is delivered via a Docker container to assist users that are leveraging Docker for their CI/CD solution.
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | If you are executing Liquibase via the command line today, you are probably doing it like so:
12 |
13 | ```console
14 | $ liquibase update --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>
15 | ```
16 |
17 | The only change to use this docker image, is to use `docker run ...` and mount the folder containing your changelog.xml (or .yml or .json or .sql) to `/liquibase/changelog` in the Liquibase container
18 |
19 | ```console
20 | $ docker run -v /home/user/changelog:/liquibase/changelog %%IMAGE%% --driver=org.postgresql.Driver --url="jdbc:postgresql://<DATABASE_IP>:<DATABASE_PORT>/<DATABASE>" --changeLogFile=/liquibase/changelog/changelog.xml --username=<USERNAME> --password=<PASSWORD>
21 | ```
22 |
23 | All Liquibase commands, such as `rollback`, `updateSQL`, and others, are available, as well.
24 |
```
--------------------------------------------------------------------------------
/wordpress/variant-cli.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:cli`
2 |
3 | This image variant does not contain WordPress itself, but instead contains [WP-CLI](https://wp-cli.org).
4 |
5 | The simplest way to use it with an existing WordPress container would be something similar to the following:
6 |
7 | ```console
8 | $ docker run -it --rm \
9 | --volumes-from some-wordpress \
10 | --network container:some-wordpress \
11 | -e WORDPRESS_DB_USER=... \
12 | -e WORDPRESS_DB_PASSWORD=... \
13 | # [and other used environment variables]
14 | %%IMAGE%%:cli user list
15 | ```
16 |
17 | Generally speaking, for WP-CLI to interact with a WordPress install, it needs access to the on-disk files of the WordPress install, and access to the database (and the easiest way to accomplish that such that `wp-config.php` does not require changes is to simply join the networking context of the existing and presumably working WordPress container, but there are many other ways to accomplish that which will be left as an exercise for the reader).
18 |
19 | **NOTE:** Since March 2021, WordPress images use a customized `wp-config.php` that pulls the values directly from the environment variables defined above (see `wp-config-docker.php` in [docker-library/wordpress#572](https://github.com/docker-library/wordpress/pull/572) and [docker-library/wordpress#577](https://github.com/docker-library/wordpress/pull/577)). As a result of reading environment variables directly, the cli container also needs the same set of environment variables to properly evaluate `wp-config.php`.
20 |
```
--------------------------------------------------------------------------------
/busybox/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is BusyBox? The Swiss Army Knife of Embedded Linux
2 |
3 | Coming in somewhere between 1 and 5 Mb in on-disk size (depending on the variant), [BusyBox](http://www.busybox.net/) is a very good ingredient to craft space-efficient distributions.
4 |
5 | BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete environment for any small or embedded system.
6 |
7 | > [wikipedia.org/wiki/BusyBox](https://en.wikipedia.org/wiki/BusyBox)
8 |
9 | %%LOGO%%
10 |
11 | # How to use this image
12 |
13 | ## Run BusyBox shell
14 |
15 | ```console
16 | $ docker run -it --rm %%IMAGE%%
17 | ```
18 |
19 | This will drop you into an `sh` shell to allow you to do what you want inside a BusyBox system.
20 |
21 | ## Create a `Dockerfile` for a binary
22 |
23 | ```dockerfile
24 | FROM %%IMAGE%%
25 | COPY ./my-static-binary /my-static-binary
26 | CMD ["/my-static-binary"]
27 | ```
28 |
29 | This `Dockerfile` will allow you to create a minimal image for your statically compiled binary. You will have to compile the binary in some other place like another container. For a simpler alternative that's similarly tiny but easier to extend, [see `alpine`](https://hub.docker.com/_/alpine/).
30 |
```
--------------------------------------------------------------------------------
/hello-world/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # Example output
2 |
3 | ```console
4 | $ docker run %%IMAGE%%
5 |
6 | Hello from Docker!
7 | This message shows that your installation appears to be working correctly.
8 |
9 | To generate this message, Docker took the following steps:
10 | 1. The Docker client contacted the Docker daemon.
11 | 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
12 | (amd64)
13 | 3. The Docker daemon created a new container from that image which runs the
14 | executable that produces the output you are currently reading.
15 | 4. The Docker daemon streamed that output to the Docker client, which sent it
16 | to your terminal.
17 |
18 | To try something more ambitious, you can run an Ubuntu container with:
19 | $ docker run -it ubuntu bash
20 |
21 | Share images, automate workflows, and more with a free Docker ID:
22 | https://hub.docker.com/
23 |
24 | For more examples and ideas, visit:
25 | https://docs.docker.com/get-started/
26 |
27 |
28 | $ docker images %%IMAGE%%
29 | REPOSITORY TAG IMAGE ID SIZE
30 | hello-world latest 74cc54e27dc4 10.07kB
31 | ```
32 |
33 | %%LOGO%%
34 |
35 | # How is this image created?
36 |
37 | This image is a prime example of using the [`scratch`](https://hub.docker.com/_/scratch/) image effectively. See [`hello.c`](%%GITHUB-REPO%%/blob/master/hello.c) in %%GITHUB-REPO%% for the source code of the `hello` binary included in this image.
38 |
39 | Because this image consists of nothing but a single static binary which prints some text to standard output, it can trivially be run as any arbitrary user (`docker run --user $RANDOM:$RANDOM %%IMAGE%%`, for example).
40 |
```
--------------------------------------------------------------------------------
/swipl/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is SWI-Prolog?
2 |
3 | SWI-Prolog is a versatile implementation of the Prolog language. Its robust multi-threading, extended data types, unbounded arithmetic and Unicode representation of text allow for natural representation of documents (e.g., XML, JSON, RDF) and exchange of data with other programming paradigms.
4 |
5 | > [wikipedia.org/wiki/Prolog](https://en.wikipedia.org/wiki/Prolog)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Start a REPL
12 |
13 | This image can be run directly to obtain an SWI-Prolog environment with most useful modules pre-built. When started without parameters, the SWI-Prolog REPL is launched automatically:
14 |
15 | ```console
16 | docker run -it %%IMAGE%%
17 | ```
18 |
19 | ## Build an image with your application
20 |
21 | It is also useful to build images on top of this base image which rely on SWI-Prolog and provide their own default command:
22 |
23 | ```dockerfile
24 | FROM %%IMAGE%%
25 | COPY . /app
26 | CMD ["swipl", "/app/start.pl"]
27 | ```
28 |
29 | This will extract and copy your source files to the image and then set the default command to run your application.
30 |
31 | ## Differences from the SWI-Prolog source distribution
32 |
33 | ### Excluded packages
34 |
35 | - jpl - interop with Java is excluded, as Java isn't included on the image
36 | - xpce - XPCE is excluded, as it's used only for the GUI platform
37 |
38 | ### Included addins
39 |
40 | This image includes several SWI-Prolog addins that are commonly used, complex to build, and require little additional space.
41 |
42 | - space
43 | - prosqlite
44 | - rocksdb\*
45 | - hdt\*
46 | - rserve_client
47 |
48 | \*excluded from ARM architecture images due to platform constraints
49 |
```
--------------------------------------------------------------------------------
/rethinkdb/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is RethinkDB?
2 |
3 | RethinkDB is an open-source, distributed database built to store JSON documents and effortlessly scale to multiple machines. It's easy to set up and learn and features a simple but powerful query language that supports table joins, groupings, aggregations, and functions.
4 |
5 | %%LOGO%%
6 |
7 | # How to use this image
8 |
9 | ## Start an instance with data mounted in the working directory
10 |
11 | The default CMD of the image is `rethinkdb --bind all`, so the RethinkDB daemon will bind to all network interfaces available to the container (by default, RethinkDB only accepts connections from `localhost`).
12 |
13 | ```bash
14 | docker run --name some-rethink -v "$PWD:/data" -d %%IMAGE%%
15 | ```
16 |
17 | ## Connect the instance to an application
18 |
19 | ```bash
20 | docker run --name some-app --link some-rethink:rdb -d application-that-uses-rdb
21 | ```
22 |
23 | ## Connecting to the web admin interface on the same host
24 |
25 | ```bash
26 | $BROWSER "http://$(docker inspect --format \
27 | '{{ .NetworkSettings.IPAddress }}' some-rethink):8080"
28 | ```
29 |
30 | # Connecting to the web admin interface on a remote / virtual host via SSH
31 |
32 | Where `remote` is an alias for the remote user@hostname:
33 |
34 | ```bash
35 | # start port forwarding
36 | ssh -fNTL localhost:8080:$(ssh remote "docker inspect --format \
37 | '{{ .NetworkSettings.IPAddress }}' some-rethink"):8080 remote
38 |
39 | # open interface in browser
40 | xdg-open http://localhost:8080
41 |
42 | # stop port forwarding
43 | kill $(lsof -t -i @localhost:8080 -sTCP:listen)
44 | ```
45 |
46 | ## Configuration
47 |
48 | See the [official docs](http://www.rethinkdb.com/docs/) for infomation on using and configuring a RethinkDB cluster.
49 |
```
--------------------------------------------------------------------------------
/solr/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Solr?
2 |
3 | Solr is the blazing-fast, open source, multi-modal search platform built on Apache Lucene. It powers full-text, vector, analytics, and geospatial search at many of the world's largest organizations. Other major features include Kubernetes integration, streaming, highlighting, faceting, and spellchecking.
4 |
5 | Learn more on [Apache Solr homepage](http://solr.apache.org/) and in the [Apache Solr Reference Guide](https://solr.apache.org/guide/).
6 |
7 | %%LOGO%%
8 |
9 | # How to use this Docker image
10 |
11 | Full documentation can be found in the [Solr Reference Guide's Docker section](https://solr.apache.org/guide/solr/latest/deployment-guide/solr-in-docker.html).
12 |
13 | To run a single Solr server:
14 |
15 | ```console
16 | $ docker run -p 8983:8983 -t %%IMAGE%%
17 | ```
18 |
19 | Then with a web browser go to http://localhost:8983/ to see the Solr Admin Console.
20 |
21 | # About this repository
22 |
23 | This repository is available on [github.com/apache/solr-docker](https://github.com/apache/solr-docker), but the image is built and maintained in the official Solr repo [github.com/apache/solr](https://github.com/apache/solr).
24 |
25 | Please direct any usage questions to the [Solr users mailing list](https://solr.apache.org/community.html#mailing-lists-chat).
26 |
27 | # History
28 |
29 | This project was started in 2015 by [Martijn Koster](https://github.com/makuk66) in the [github.com/docker-solr/docker-solr](https://github.com/docker-solr/docker-solr) repository. In 2019, the maintainership and copyright was transferred to the Apache Solr project. Many thanks to Martijn for all your contributions over the years!
30 |
```
--------------------------------------------------------------------------------
/swift/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Swift?
2 |
3 | Swift is a high-performance system programming language. It has a clean and modern syntax, offers seamless access to existing C and Objective-C code and frameworks, and is memory safe by default.
4 |
5 | Although inspired by Objective-C and many other languages, Swift is not itself a C-derived language. As a complete and independent language, Swift packages core features like flow control, data structures, and functions, with high-level constructs like objects, protocols, closures, and generics. Swift embraces modules, eliminating the need for headers and the code duplication they entail.
6 |
7 | To learn more about the programming language, visit [swift.org](https://swift.org).
8 |
9 | > [swift.org](https://swift.org/about/)
10 | > [Swift on Github](https://github.com/apple/swift)
11 |
12 | %%LOGO%%
13 |
14 | # How to use this image
15 |
16 | ##### Start a REPL
17 |
18 | Swift requires [a little bit of extra security privilege](https://github.com/apple/swift-docker/issues/9#issuecomment-272527182) to run the REPL. The following command creates an ephemeral container, attaches your terminal to it and starts the Swift REPL. A great way to try out pre-release builds!
19 |
20 | ```bash
21 | docker run --cap-add sys_ptrace -it --rm %%IMAGE%% swift
22 | ```
23 |
24 | ##### Pull the Docker Image From Docker Hub:
25 |
26 | ```bash
27 | docker pull %%IMAGE%%
28 | ```
29 |
30 | ##### Create a Container from the Image and Attach It:
31 |
32 | ```bash
33 | docker run -it --name swiftfun %%IMAGE%% /bin/bash
34 | ```
35 |
36 | ##### To Start and Attach Your Image Later:
37 |
38 | Start your image with name `swiftfun`
39 |
40 | ```bash
41 | docker start swiftfun
42 | ```
43 |
44 | and then attach it
45 |
46 | ```bash
47 | docker attach swiftfun
48 | ```
49 |
```
--------------------------------------------------------------------------------
/erlang/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Erlang?
2 |
3 | Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.
4 |
5 | > [wikipedia.org/wiki/Erlang_(programming_language)](https://en.wikipedia.org/wiki/Erlang_%28programming_language%29)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Run it as the REPL
12 |
13 | ```console
14 | ➸ docker run -it --rm %%IMAGE%%
15 | Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]
16 |
17 | Eshell V9.0 (abort with ^G)
18 | 1> uptime().
19 | 3 seconds
20 | ok
21 | 2> % use Ctrl+G to call the shell switch
22 | User switch command
23 | --> ?
24 | c [nn] - connect to job
25 | i [nn] - interrupt job
26 | k [nn] - kill job
27 | j - list all jobs
28 | s [shell] - start local shell
29 | r [node [shell]] - start remote shell
30 | q - quit erlang
31 | ? | h - this message
32 | --> q
33 | ➸ docker run -it --rm -h erlang.local %%IMAGE%% erl -name [email protected]
34 | Erlang/OTP 20 [erts-9.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]
35 |
36 | Eshell V9.0 (abort with ^G)
37 | ([email protected])1> erlang:system_info(otp_release).
38 | "20"
39 | ([email protected])2>
40 | User switch command
41 | --> q
42 | ```
43 |
44 | ## Run a single Erlang escript
45 |
46 | ```console
47 | $ docker run -it --rm --name %%REPO%%-inst1 -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%% escript your-escript.erl
48 | ```
49 |
```
--------------------------------------------------------------------------------
/photon/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # VMware Photon OS
2 |
3 | %%LOGO%%
4 |
5 | Photon OS is an open source minimal Linux container host optimized for cloud-native applications, cloud platforms, and VMware infrastructure. It is designed to have a small footprint and boot extremely quickly on VMware platforms. Photon OS is intended to invite collaboration around running containerized applications in a virtualized environment.
6 |
7 | Photon contains `tdnf`, a new, open-source, yum-compatible package manager that will help make the system as small as possible, but preserve the robust yum package management capabilities.
8 |
9 | See the [FAQ](http://vmware.github.io/photon/assets/files/photon_faqs.pdf) for more information.
10 |
11 | ## How to use these images
12 |
13 | Photon OS images are intended for use in the **FROM** field of an application's `Dockerfile`. For example, to use VMware Photon 1.0GA as the base of an image, specify `FROM %%IMAGE%%:1.0GA`.
14 |
15 | ## Support
16 |
17 | Photon OS is released as open source software and comes with no commercial support.
18 |
19 | But since we want to ensure success and recognize that Photon OS™ consumers might fall into a range of roles - from developers that are steeped in the conventions of open-source to customers that are more accustomed to VMware commercial offerings, we offer several methods of engaging with the Photon OS team and community.
20 |
21 | For our developer community, feel free to join our Google groups at [vmware-photon-os-dev](https://groups.google.com/forum/#%21forum/vmware-photon-dev)
22 |
23 | For more general user questions, visit the Photon OS user forum in our [Photon OS VMware Community](http://communities.vmware.com/community/vmtn/devops/project-photon).
24 |
```
--------------------------------------------------------------------------------
/clickhouse/logo.svg:
--------------------------------------------------------------------------------
```
1 | <?xml version="1.0" encoding="UTF-8"?>
2 | <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 616 616">
3 | <defs>
4 | <style>
5 | .cls-1 {
6 | clip-path: url(#clippath);
7 | }
8 |
9 | .cls-2 {
10 | fill: none;
11 | }
12 |
13 | .cls-2, .cls-3, .cls-4 {
14 | stroke-width: 0px;
15 | }
16 |
17 | .cls-3 {
18 | fill: #1e1e1e;
19 | }
20 |
21 | .cls-4 {
22 | fill: #faff69;
23 | }
24 | </style>
25 | <clipPath id="clippath">
26 | <rect class="cls-2" x="83.23" y="71.73" width="472.55" height="472.55"/>
27 | </clipPath>
28 | </defs>
29 | <g id="Layer_2" data-name="Layer 2">
30 | <rect class="cls-4" width="616" height="616"/>
31 | </g>
32 | <g id="Layer_1" data-name="Layer 1">
33 | <g class="cls-1">
34 | <g>
35 | <path class="cls-3" d="m120.14,113.3c0-2.57,2.09-4.66,4.66-4.66h34.98c2.57,0,4.66,2.09,4.66,4.66v389.38c0,2.57-2.09,4.66-4.66,4.66h-34.98c-2.57,0-4.66-2.09-4.66-4.66V113.3Z"/>
36 | <path class="cls-3" d="m208.75,113.3c0-2.57,2.09-4.66,4.66-4.66h34.98c2.57,0,4.66,2.09,4.66,4.66v389.38c0,2.57-2.09,4.66-4.66,4.66h-34.98c-2.57,0-4.66-2.09-4.66-4.66V113.3Z"/>
37 | <path class="cls-3" d="m297.35,113.3c0-2.57,2.09-4.66,4.66-4.66h34.98c2.57,0,4.66,2.09,4.66,4.66v389.38c0,2.57-2.09,4.66-4.66,4.66h-34.98c-2.57,0-4.66-2.09-4.66-4.66V113.3Z"/>
38 | <path class="cls-3" d="m385.94,113.3c0-2.57,2.09-4.66,4.66-4.66h34.98c2.57,0,4.66,2.09,4.66,4.66v389.38c0,2.57-2.09,4.66-4.66,4.66h-34.98c-2.57,0-4.66-2.09-4.66-4.66V113.3Z"/>
39 | <path class="cls-3" d="m474.56,268.36c0-2.57,2.09-4.66,4.66-4.66h34.98c2.57,0,4.65,2.09,4.65,4.66v79.28c0,2.57-2.09,4.66-4.65,4.66h-34.98c-2.57,0-4.66-2.09-4.66-4.66v-79.28Z"/>
40 | </g>
41 | </g>
42 | </g>
43 | </svg>
```
--------------------------------------------------------------------------------
/pypy/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is PyPy?
2 |
3 | PyPy is a Python interpreter and just-in-time compiler. PyPy focuses on speed, efficiency and compatibility with the original CPython interpreter.
4 |
5 | PyPy started out as a Python interpreter written in the Python language itself. Current PyPy versions are translated from RPython to C code and compiled. The PyPy JIT (short for "Just In Time") compiler is capable of turning Python code into machine code at run time.
6 |
7 | > [wikipedia.org/wiki/PyPy](https://en.wikipedia.org/wiki/PyPy)
8 |
9 | %%LOGO%%
10 |
11 | # How to use this image
12 |
13 | ## Create a `Dockerfile` in your Python app project
14 |
15 | ```dockerfile
16 | FROM %%IMAGE%%:3
17 |
18 | WORKDIR /usr/src/app
19 |
20 | COPY requirements.txt ./
21 | RUN pip install --no-cache-dir -r requirements.txt
22 |
23 | COPY . .
24 |
25 | CMD [ "pypy3", "./your-daemon-or-script.py" ]
26 | ```
27 |
28 | or (if you need to use Python 2):
29 |
30 | ```dockerfile
31 | FROM %%IMAGE%%:2
32 |
33 | WORKDIR /usr/src/app
34 |
35 | COPY requirements.txt ./
36 | RUN pip install --no-cache-dir -r requirements.txt
37 |
38 | COPY . .
39 |
40 | CMD [ "pypy", "./your-daemon-or-script.py" ]
41 | ```
42 |
43 | You can then build and run the Docker image:
44 |
45 | ```console
46 | $ docker build -t my-python-app .
47 | $ docker run -it --rm --name my-running-app my-python-app
48 | ```
49 |
50 | ## Run a single Python script
51 |
52 | For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Python script by using the Python Docker image directly:
53 |
54 | ```console
55 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:3 pypy3 your-daemon-or-script.py
56 | ```
57 |
58 | or (again, if you need to use Python 2):
59 |
60 | ```console
61 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:2 pypy your-daemon-or-script.py
62 | ```
63 |
```
--------------------------------------------------------------------------------
/docker/variant-rootless.md:
--------------------------------------------------------------------------------
```markdown
1 | ## `%%IMAGE%%:<version>-rootless`
2 |
3 | For more information about using the experimental "rootless" image variants, see [docker-library/docker#174](https://github.com/docker-library/docker/pull/174).
4 |
5 | **Note:** just like the regular `dind` images, `--privileged` is required for Docker-in-Docker to function properly ([docker-library/docker#151](https://github.com/docker-library/docker/issues/151#issuecomment-483185972) & [docker-library/docker#281](https://github.com/docker-library/docker/issues/281#issuecomment-744766015)), which is a security issue that needs to be treated appropriately.
6 |
7 | Basic example usage:
8 |
9 | ```console
10 | $ docker run -d --name some-docker --privileged %%IMAGE%%:dind-rootless
11 | $ docker logs --tail=3 some-docker # to verify the daemon has finished generating TLS certificates and is listening successfully
12 | time="xxx" level=info msg="Daemon has completed initialization"
13 | time="xxx" level=info msg="API listen on /run/user/1000/docker.sock"
14 | time="xxx" level=info msg="API listen on [::]:2376"
15 | $ docker exec -it some-docker docker-entrypoint.sh sh # using "docker-entrypoint.sh" which auto-sets "DOCKER_HOST" appropriately
16 | / $ docker info --format '{{ json .SecurityOptions }}'
17 | ["name=seccomp,profile=default","name=rootless"]
18 | ```
19 |
20 | To run with a different UID/GID than the one baked into the image, modify `/etc/passwd`, `/etc/group`, and filesystem permissions (especially for the `rootless` user's home directory) as appropriate; for example:
21 |
22 | ```dockerfile
23 | FROM %%IMAGE%%:dind-rootless
24 | USER root
25 | RUN set -eux; \
26 | sed -i -e 's/^rootless:x:1000:1000:/rootless:x:1234:5678:/' /etc/passwd; \
27 | sed -i -e 's/^rootless:x:1000:/rootless:x:5678:/' /etc/group; \
28 | chown -R rootless ~rootless
29 | USER rootless
30 | ```
31 |
```
--------------------------------------------------------------------------------
/dart/logo.svg:
--------------------------------------------------------------------------------
```
1 | <?xml version="1.0" encoding="utf-8"?>
2 | <!-- Generator: Adobe Illustrator 22.0.1, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
3 | <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
4 | width="192px" height="192px" viewBox="0 0 192 192" enable-background="new 0 0 192 192" xml:space="preserve">
5 | <g>
6 | <rect x="0" fill="none" width="192" height="192"/>
7 | <path fill="#01579B" d="M51,141l-26-26c-3.08-3.17-5-7.63-5-12c0-2.02,1.14-5.18,2-7l24-50L51,141z"/>
8 | <path fill="#40C4FF" d="M140,51l-26-26c-2.27-2.28-7-5-11-5c-3.44,0-6.81,0.69-9,2L46,46L140,51z"/>
9 | <polygon fill="#40C4FF" points="82,172 145,172 145,145 98,130 55,145 "/>
10 | <path fill="#29B6F6" d="M46,127c0,8.02,1.01,9.99,5,14l4,4h90l-44-50L46,46V127z"/>
11 | <path fill="#01579B" d="M126,46H46l99,99h27V83l-32-32C135.51,46.49,131.51,46,126,46z"/>
12 | <path opacity="0.2" fill="#FFFFFF" d="M52,142c-4-4.02-5-7.97-5-15V47l-1-1v81C46,134.03,46,135.98,52,142l3,3l0,0L52,142z"/>
13 | <polygon opacity="0.2" fill="#263238" points="171,82 171,144 144,144 145,145 172,145 172,83 "/>
14 | <path opacity="0.2" fill="#FFFFFF" d="M140,51c-4.96-4.96-9.02-5-15-5H46l1,1h78C127.99,47,135.52,46.5,140,51L140,51z"/>
15 | <radialGradient id="SVGID_1_" cx="96" cy="96" r="76" gradientUnits="userSpaceOnUse">
16 | <stop offset="0" style="stop-color:#FFFFFF;stop-opacity:0.1"/>
17 | <stop offset="1" style="stop-color:#FFFFFF;stop-opacity:0"/>
18 | </radialGradient>
19 | <path opacity="0.2" fill="url(#SVGID_1_)" d="M171,82l-31-31l-26-26c-2.27-2.28-7-5-11-5c-3.44,0-6.81,0.69-9,2L46,46L22,96
20 | c-0.86,1.82-2,4.98-2,7c0,4.37,1.92,8.83,5,12l23.96,23.79c0.57,0.7,1.25,1.42,2.04,2.21l1,1l3,3l26,26l1,1h62h1v-27h27v-0.07V83
21 | L171,82z"/>
22 | </g>
23 | </svg>
24 |
```
--------------------------------------------------------------------------------
/buildpack-deps/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is `buildpack-deps`?
2 |
3 | In spirit, `buildpack-deps` is similar to [Heroku's stack images](https://github.com/heroku/stack-images/blob/master/bin/cedar.sh). It includes a large number of "development header" packages needed by various things like Ruby Gems, PyPI modules, etc. For example, `buildpack-deps` would let you do a `bundle install` in an arbitrary application directory without knowing beforehand that `ssl.h` is required to build a dependent module.
4 |
5 | %%LOGO%%
6 |
7 | # How to use this image
8 |
9 | This stack is designed to be the foundation of a language-stack image.
10 |
11 | ## What's included?
12 |
13 | The main tags of this image are the full batteries-included approach. With them, a majority of arbitrary `gem install` / `npm install` / `pip install` should be successful without additional header/development packages.
14 |
15 | For some language stacks, that doesn't make sense, particularly if linking to arbitrary external C libraries is much less common (as in Go and Java, for example), which is where these other smaller variants can come in handy.
16 |
17 | ### `curl`
18 |
19 | This variant includes just the `curl`, `wget`, and `ca-certificates` packages. This is perfect for cases like the Java JRE, where downloading JARs is very common and necessary, but checking out code isn't.
20 |
21 | ### `scm`
22 |
23 | This variant is based on `curl`, but also adds various source control management tools. As of this writing, the current list of included tools is `bzr`, `git`, `hg`, and `svn`. Intentionally missing is `cvs` due to the dwindling relevance it has (sorry CVS). This image is perfect for cases like the Java JDK, where downloading JARs is very common (hence the `curl` base still), but checking out code also becomes more common as well (compared to the JRE).
24 |
```
--------------------------------------------------------------------------------
/ibm-semeru-runtimes/logo.svg:
--------------------------------------------------------------------------------
```
1 | <svg id="SemeruRuntimes" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 32 32"><defs><linearGradient id="mowig1tk4a" x1="-66.645" y1="-182.5" x2="-58.418" y2="-182.5" gradientTransform="translate(79.458 204.458)" gradientUnits="userSpaceOnUse"><stop offset=".071"/><stop offset=".964" stop-opacity="0"/></linearGradient><linearGradient id="ahawze7n2b" x1="2057.037" y1="-1935.038" x2="2062.733" y2="-1935.038" gradientTransform="matrix(1.978 0 0 .583 -4065.838 1144.613)" gradientUnits="userSpaceOnUse"><stop offset=".096"/><stop offset=".964" stop-opacity="0"/></linearGradient><linearGradient id="y76v2m5qld" x1=".098" y1="31.902" x2="31.702" y2=".298" gradientUnits="userSpaceOnUse"><stop offset=".1" stop-color="#ee5396"/><stop offset=".9" stop-color="#8a3ffc"/></linearGradient><mask id="ozj5xxp58c" x="0" y="0" width="32" height="32" maskUnits="userSpaceOnUse"><path d="M25.5 28h-8a4.491 4.491 0 0 1-1.326-8.784 5.472 5.472 0 0 1 10.652 0A4.491 4.491 0 0 1 25.5 28zm-4-11a3.477 3.477 0 0 0-3.459 3.146l-.08.789-.785.1A2.492 2.492 0 0 0 17.5 26h8a2.492 2.492 0 0 0 .324-4.963l-.785-.1-.08-.789A3.477 3.477 0 0 0 21.5 17z" style="fill:#fff"/><path transform="rotate(-90 17 21.958)" style="fill:url(#mowig1tk4a)" d="M12.666 16.958h8.667v10h-8.667z" id="Gradients_black_" data-name="Gradients (black)"/><path d="M23 28H3a1 1 0 0 1-.861-1.509l8.864-15 1.722 1.018L4.752 26H23z" style="fill:#fff"/><path transform="rotate(121.2 9.061 17)" style="fill:url(#ahawze7n2b)" d="M3.127 14.96h11.869v4.079H3.127z" id="Gradients_black_2" data-name="Gradients (black)"/></mask></defs><g style="mask:url(#ozj5xxp58c)"><path style="fill:url(#y76v2m5qld)" d="M0 0h32v32H0z"/></g><path style="fill:#001d6c" d="M13.025 12 16 6.966 18.975 12h2.323L16 3.034 10.702 12h2.323z"/></svg>
```
--------------------------------------------------------------------------------
/almalinux/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # AlmaLinux OS
2 |
3 | [AlmaLinux OS](https://almalinux.org/) is an Open Source and forever-free enterprise Linux distribution, governed and driven by the community, focused on long-term stability and a robust production-grade platform. AlmaLinux OS is binary compatible with RHEL®, and it was founded by the team behind the well-established [CloudLinux OS](https://www.cloudlinux.com/all-products/product-overview/cloudlinuxos). Today, the AlmaLinux OS Foundation, run by a community-elected board of directors, owns and manages the operating system.
4 |
5 | %%LOGO%%
6 |
7 | # About this image
8 |
9 | ## Platform image
10 |
11 | The default (platform) image is a general-purpose image with a full DNF stack and basic tools like find, tar, vi, etc.
12 |
13 | The `%%IMAGE%%:latest` tag will always point to the latest stable release of the default image. Major releases and minor releases are also tagged with their version (e.g. `%%IMAGE%%:8` or `%%IMAGE%%:8.4`).
14 |
15 | ## Minimal image
16 |
17 | The minimal image is a stripped-down image that uses the microdnf package manager and contains a very limited package set. It is designed for applications that come with their own dependencies bundled (e.g. NodeJS, Python).
18 |
19 | The `%%IMAGE%%:minimal` tag always points to the most recent version of the minimal image. Tags for major (e.g. `%%IMAGE%%:8-minimal`) and minor (e.g. `%%IMAGE%%:8.4-minimal`) releases are also available.
20 |
21 | ### Upgrade policy
22 |
23 | All images for supported releases will be updated monthly or as needed for security fixes.
24 |
25 | ## How It's Made
26 |
27 | The rootfs tarballs for this image are built using the [livemedia-creator tool](http://weldr.io/lorax/livemedia-creator.html). The build script and kickstart files are available in the [AlmaLinux/docker-images](https://github.com/AlmaLinux/docker-images) git repository.
28 |
```
--------------------------------------------------------------------------------
/spark/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Apache Spark™?
2 |
3 | Apache Spark™ is a multi-language engine for executing data engineering, data science, and machine learning on single-node machines or clusters. It provides high-level APIs in Scala, Java, Python, and R, and an optimized engine that supports general computation graphs for data analysis. It also supports a rich set of higher-level tools including Spark SQL for SQL and DataFrames, pandas API on Spark for pandas workloads, MLlib for machine learning, GraphX for graph processing, and Structured Streaming for stream processing.
4 |
5 | %%LOGO%%
6 |
7 | ## Online Documentation
8 |
9 | You can find the latest Spark documentation, including a programming guide, on the [project web page](https://spark.apache.org/documentation.html). This README file only contains basic setup instructions.
10 |
11 | ## Interactive Scala Shell
12 |
13 | The easiest way to start using Spark is through the Scala shell:
14 |
15 | ```console
16 | docker run -it %%IMAGE%% /opt/spark/bin/spark-shell
17 | ```
18 |
19 | Try the following command, which should return 1,000,000,000:
20 |
21 | ```scala
22 | scala> spark.range(1000 * 1000 * 1000).count()
23 | ```
24 |
25 | ## Interactive Python Shell
26 |
27 | The easiest way to start using PySpark is through the Python shell:
28 |
29 | ```console
30 | docker run -it %%IMAGE%%:python3 /opt/spark/bin/pyspark
31 | ```
32 |
33 | And run the following command, which should also return 1,000,000,000:
34 |
35 | ```python
36 | >>> spark.range(1000 * 1000 * 1000).count()
37 | ```
38 |
39 | ## Interactive R Shell
40 |
41 | The easiest way to start using R on Spark is through the R shell:
42 |
43 | ```console
44 | docker run -it %%IMAGE%%:r /opt/spark/bin/sparkR
45 | ```
46 |
47 | ## Running Spark on Kubernetes
48 |
49 | https://spark.apache.org/docs/latest/running-on-kubernetes.html
50 |
51 | ## Configuration and environment variables
52 |
53 | See more in https://github.com/apache/spark-docker/blob/master/OVERVIEW.md#environment-variable
54 |
```
--------------------------------------------------------------------------------
/logstash/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Logstash?
2 |
3 | Logstash is an open source data collection engine with real-time pipelining capabilities. Logstash can dynamically unify data from disparate sources and normalize the data into destinations of your choice.
4 |
5 | Collection is accomplished via a number of configurable input plugins including raw socket/packet communication, file tailing and several message bus clients. Once an input plugin has collected data it can be processed by any number of filters which modify and annotate the event data. Finally, events are routed to output plugins which can forward the events to a variety of external programs including Elasticsearch, local files and several message bus implementations.
6 |
7 | > For more information about Logstash, please visit [www.elastic.co/products/logstash](https://www.elastic.co/products/logstash)
8 |
9 | %%LOGO%%
10 |
11 | # About This Image
12 |
13 | This default distribution is governed by the Elastic License and includes the [full set of free features](https://www.elastic.co/subscriptions).
14 |
15 | View the detailed release notes [here](https://www.elastic.co/guide/en/logstash/current/releasenotes.html).
16 |
17 | Not the version you're looking for? View all supported [past releases](https://www.docker.elastic.co).
18 |
19 | # How to use this image
20 |
21 | **Note:** Pulling an image requires using a specific version number tag. The `latest` tag is not supported.
22 |
23 | For Logstash versions prior to 6.4.0, a full list of images, tags, and documentation can be found at [docker.elastic.co](https://www.docker.elastic.co/).
24 |
25 | For full Logstash documentation see [here](https://www.elastic.co/guide/en/logstash/current/index.html).
26 |
27 | For instructions specifically related to running the Docker image, see [this section](https://www.elastic.co/guide/en/logstash/current/docker-config.html) of the Logstash documentation.
28 |
```
--------------------------------------------------------------------------------
/rocket.chat/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # Rocket.Chat
2 |
3 | Rocket.Chat is a Web Chat Server, developed in JavaScript, using the Meteor fullstack framework.
4 |
5 | It is a great solution for communities and companies wanting to privately host their own chat service or for developers looking forward to build and evolve their own chat platforms.
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | First, start an instance of mongo and initiate replicaSet:
12 |
13 | ```console
14 | $ docker run --name db -d mongo:4.0 --smallfiles --replSet rs0 --oplogSize 128
15 | ```
16 |
17 | ```console
18 | $ docker exec -ti db mongo --eval "printjson(rs.initiate())"
19 | ```
20 |
21 | Then start Rocket.Chat linked to this mongo instance:
22 |
23 | ```console
24 | $ docker run --name rocketchat --link db --env MONGO_OPLOG_URL=mongodb://db:27017/local -d %%IMAGE%%
25 | ```
26 |
27 | This will start a Rocket.Chat instance listening on the default Meteor port of 3000 on the container.
28 |
29 | If you'd like to be able to access the instance directly at standard port on the host machine:
30 |
31 | ```console
32 | $ docker run --name rocketchat -p 80:3000 --link db --env ROOT_URL=http://localhost --env MONGO_OPLOG_URL=mongodb://db:27017/local -d %%IMAGE%%
33 | ```
34 |
35 | Then, access it via `http://localhost` in a browser. Replace `localhost` in `ROOT_URL` with your own domain name if you are hosting at your own domain.
36 |
37 | If you're using a third party Mongo provider, or working with Kubernetes, you need to override the `MONGO_URL` environment variable:
38 |
39 | ```console
40 | $ docker run --name rocketchat -p 80:3000 --env ROOT_URL=http://localhost --env MONGO_URL=mongodb://mymongourl/mydb --env MONGO_OPLOG_URL=mongodb://mymongourl:27017/local -d %%IMAGE%%
41 | ```
42 |
43 | ### Check our docs
44 |
45 | For full documentation on production deployment best practices, please visit https://rocket.chat/docs/installation/docker-containers/
46 |
47 | Need some help? Join our community forums https://forums.rocket.chat
48 |
```
--------------------------------------------------------------------------------
/gcc/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is GCC?
2 |
3 | The GNU Compiler Collection (GCC) is a compiler system produced by the GNU Project that supports various programming languages. GCC is a key component of the GNU toolchain. The Free Software Foundation (FSF) distributes GCC under the GNU General Public License (GNU GPL). GCC has played an important role in the growth of free software, as both a tool and an example.
4 |
5 | > [wikipedia.org/wiki/GNU_Compiler_Collection](https://en.wikipedia.org/wiki/GNU_Compiler_Collection)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Start a GCC instance running your app
12 |
13 | The most straightforward way to use this image is to use a gcc container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
14 |
15 | ```dockerfile
16 | FROM %%IMAGE%%:4.9
17 | COPY . /usr/src/myapp
18 | WORKDIR /usr/src/myapp
19 | RUN gcc -o myapp main.c
20 | CMD ["./myapp"]
21 | ```
22 |
23 | Then, build and run the Docker image:
24 |
25 | ```console
26 | $ docker build -t my-gcc-app .
27 | $ docker run -it --rm --name my-running-app my-gcc-app
28 | ```
29 |
30 | ## Compile your app inside the Docker container
31 |
32 | There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
33 |
34 | ```console
35 | $ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:4.9 gcc -o myapp myapp.c
36 | ```
37 |
38 | This will add your current directory, as a volume, to the container, set the working directory to the volume, and run the command `gcc -o myapp myapp.c.` This tells gcc to compile the code in `myapp.c` and output the executable to myapp. Alternatively, if you have a `Makefile`, you can instead run the `make` command inside your container:
39 |
40 | ```console
41 | $ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:4.9 make
42 | ```
43 |
```
--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
```dockerfile
1 | FROM perl:5.39-bookworm
2 |
3 | RUN set -eux; \
4 | apt-get update; \
5 | apt-get install -y --no-install-recommends \
6 | vim \
7 | # https://bugs.debian.org/763056 - SVG rendering in ImageMagick looks awful unless it can use inkscape to render (or RSVG, which is explicitly not compiled into the Debian package??)
8 | inkscape \
9 | ; \
10 | rm -rf /var/lib/apt/lists/*
11 |
12 | # secure by default ♥ (thanks to sri!)
13 | ENV PERL_CPANM_OPT --verbose --mirror https://cpan.metacpan.org
14 | # TODO find a way to make --mirror-only / SSL work with backpan too :(
15 | RUN cpanm Digest::SHA Module::Signature
16 | # TODO find a way to make --verify work with backpan as well :'(
17 | #ENV PERL_CPANM_OPT $PERL_CPANM_OPT --verify
18 |
19 | # reinstall cpanm itself, for good measure
20 | RUN cpanm App::cpanminus
21 |
22 | RUN cpanm [email protected]
23 |
24 | RUN cpanm EV
25 | RUN cpanm IO::Socket::IP
26 | RUN cpanm --notest IO::Socket::SSL
27 | # the tests for IO::Socket::SSL like to hang... :(
28 |
29 | RUN cpanm Term::UI
30 |
31 | ENV LANG C.UTF-8
32 |
33 | RUN mkdir ~/.vim ~/.vim/bundle ~/.vim/autoload
34 | RUN set -x \
35 | && git clone https://github.com/tpope/vim-pathogen.git ~/.vim/bundle/pathogen \
36 | && ln -s ../bundle/pathogen/autoload/pathogen.vim ~/.vim/autoload/
37 | RUN git clone https://github.com/jtratner/vim-flavored-markdown.git ~/.vim/bundle/ghmarkdown
38 | RUN git clone https://github.com/nanotech/jellybeans.vim.git ~/.vim/bundle/jellybeans
39 | RUN { \
40 | echo 'scriptencoding utf-8'; \
41 | \
42 | echo 'execute pathogen#infect()'; \
43 | \
44 | echo 'syntax on'; \
45 | echo 'filetype plugin indent on'; \
46 | echo 'set list listchars=tab:»·,nbsp:_,extends:¬ noet ts=4 sw=4 nobackup noswapfile'; \
47 | \
48 | echo 'set background=dark'; \
49 | echo 'colorscheme jellybeans'; \
50 | \
51 | echo 'au FilterWritePre * if &diff | setlocal wrap< | endif'; \
52 | \
53 | echo 'au BufNewFile,BufRead *.md,*.markdown setlocal filetype=ghmarkdown'; \
54 | } > ~/.vimrc
55 |
56 | COPY . /usr/src/docker-library-docs
57 | WORKDIR /usr/src/docker-library-docs
58 |
59 | CMD ["./push.pl"]
60 |
```
--------------------------------------------------------------------------------
/haxe/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Haxe?
2 |
3 | [Haxe](https://haxe.org) is an open source toolkit based on a modern, high level, strictly typed programming language, a cross-compiler, a complete cross-platform standard library and ways to access each platform's native capabilities.
4 |
5 | The Haxe compiler can output a number of source and binary files. As of Haxe 3.4.0-rc.1, the Haxe compiler can target JavaScript, Java, C#, C++, Python, PHP, Flash SWF, ActionScript 3, Lua, and Neko.
6 |
7 | %%LOGO%%
8 |
9 | # About this image
10 |
11 | This image ships a minimal Haxe toolkit:
12 |
13 | - the `haxe` compiler with its standard library
14 | - the `haxelib` library manager
15 | - the `neko` virtual machine
16 |
17 | # How to use this image
18 |
19 | The most straightforward way to use this image is to use a Haxe container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
20 |
21 | ```dockerfile
22 | FROM %%IMAGE%%:3.4
23 |
24 | RUN mkdir -p /usr/src/app
25 | WORKDIR /usr/src/app
26 |
27 | # install dependencies
28 | COPY *.hxml /usr/src/app/
29 | RUN yes | haxelib install all
30 |
31 | # compile the project
32 | COPY . /usr/src/app
33 | RUN haxe build.hxml
34 |
35 | # run the output when the container starts
36 | CMD ["neko", "Main.n"]
37 | ```
38 |
39 | Then, build and run the Docker image:
40 |
41 | ```console
42 | $ docker build -t my-haxe-app .
43 | $ docker run -it --rm --name my-running-app my-haxe-app
44 | ```
45 |
46 | ## Using the onbuild variants
47 |
48 | There are `onbuild` variants that include multiple `ONBUILD` triggers to perform all of the steps in the above Dockerfile, except there is no `CMD` instruction for running the compilation output.
49 |
50 | Rewriting the above Dockerfile with `%%IMAGE%%:3.4-onbuild`, we will get:
51 |
52 | ```dockerfile
53 | FROM %%IMAGE%%:3.4-onbuild
54 |
55 | # run the output when the container starts
56 | CMD ["neko", "Main.n"]
57 | ```
58 |
59 | The `onbuild` variants assume the main compilation hxml file is named `build.hxml`. To use another hxml file, set the `BUILD_HXML` build argument during build:
60 |
61 | ```console
62 | $ docker build -t my-haxe-app --build-arg BUILD_HXML=compile.hxml .
63 | ```
64 |
```
--------------------------------------------------------------------------------
/elasticsearch/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Elasticsearch?
2 |
3 | Elasticsearch is a distributed, RESTful search and analytics engine capable of solving a growing number of use cases. As the heart of the Elastic Stack, it centrally stores your data so you can discover the expected and uncover the unexpected.
4 |
5 | > For more information about Elasticsearch, please visit [www.elastic.co/products/elasticsearch](https://www.elastic.co/products/elasticsearch)
6 |
7 | %%LOGO%%
8 |
9 | # About This Image
10 |
11 | This default distribution is governed by the Elastic License, and includes the [full set of free features](https://www.elastic.co/subscriptions).
12 |
13 | View the detailed release notes [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-release-notes.html).
14 |
15 | Not the version you're looking for? View all supported [past releases](https://www.docker.elastic.co).
16 |
17 | # How to use this image
18 |
19 | **Note:** Pulling an images requires using a specific version number tag. The `latest` tag is not supported.
20 |
21 | For Elasticsearch versions prior to 6.4.0 a full list of images, tags, and documentation can be found at [docker.elastic.co](https://www.docker.elastic.co/).
22 |
23 | For full Elasticsearch documentation see [here](https://www.elastic.co/guide/en/elasticsearch/reference/index.html).
24 |
25 | **The commands below are intended for deploying in a development context only. For production installation and configuration, see [Install Elasticsearch with Docker](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/docker.html).**
26 |
27 | ## Running in Development Mode
28 |
29 | Create user defined network (useful for connecting to other services attached to the same network (e.g. Kibana)):
30 |
31 | ```console
32 | $ docker network create somenetwork
33 | ```
34 |
35 | Run Elasticsearch:
36 |
37 | ```console
38 | $ docker run -d --name elasticsearch --net somenetwork -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:tag
39 | ```
40 |
41 | ## Running in Production Mode
42 |
43 | See [Install Elasticsearch with Docker](https://www.elastic.co/guide/en/elasticsearch/reference/7.5/docker.html)
44 |
```
--------------------------------------------------------------------------------
/api-firewall/logo.svg:
--------------------------------------------------------------------------------
```
1 | <?xml version="1.0" encoding="utf-8"?>
2 | <!-- Generator: Adobe Illustrator 19.2.1, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
3 | <svg version="1.1" id="layer" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
4 | viewBox="0 0 652 652" style="enable-background:new 0 0 652 652;" xml:space="preserve" width="250" height="168">
5 | <style type="text/css">
6 | .st0{fill:#FF5D18;}
7 | </style>
8 | <path class="st0" d="M572.5,257.4v-57L458.2,251v-72.9l-115.6,51.3v115.4l114.3-50.7v33.4l114.2-50.6v20.3l54.9-24.4v-39.1
9 | L572.5,257.4"/>
10 | <path d="M124,444.8l18.6-62.1h20.9L133.7,474H115l-20.4-62l-20.5,62H55.5L26,382.6h21.4l18.3,62.1l20.2-62.5h17.8L124,444.8
11 | M263.5,474h20.8V344.8h-20.8V474z M296.8,474h20.8V344.8h-20.8L296.8,474z M447.3,474H426V384h21.3v20.3
12 | c5.8-13.5,16.5-22.7,32.9-22v21.8h-1.2c-18.6,0-31.7,11.8-31.7,35.6V474z M594.3,382.3c19.7,0,31.7,12.4,31.7,34.4V474h-20.7v-51
13 | c0-14.3-6.7-21.9-18.3-21.9c-11.3,0-19.3,7.8-19.3,22.3V474h-20.7v-51.2c0-14-6.8-21.8-18.3-21.8c-11.5,0-19.4,8.5-19.4,22.4V474
14 | h-20.7v-89.8h20.7v13.6c5.8-8,13.7-15.5,27.6-15.5c13,0,22.1,6.3,26.9,15.8C571,388.6,580.6,382.3,594.3,382.3 M393.1,440.1
15 | c0,11.1-10.4,18.6-24.4,18.6c-9.9,0-17.7-4.7-17.7-13.1v-0.3c0-9,7.8-14.2,21-14.2c8.2,0,15.7,1.5,21.1,3.5L393.1,440.1z
16 | M373.1,382.3c-11.3,0-19.7,1.7-27.4,4.4v18.5c7.7-2.9,15-4.8,24.5-4.8c14.6,0,22.6,6.7,22.6,18.9v2.2c-7.1-2.2-14.3-3.7-25.4-3.7
17 | c-21.4,0-37.2,9.4-37.2,28.5v0.3c0,17.8,15.3,27.3,32.7,27.3c13.9,0,23.5-5.5,29.8-12.7v10.9h20.9v-52.5
18 | C413.5,396,400.3,382.3,373.1,382.3L373.1,382.3z M226.5,440.1c0,11.1-10.4,18.6-24.4,18.6c-9.9,0-17.7-4.7-17.7-13.1v-0.3
19 | c0-9,7.8-14.2,21.1-14.2c8.2,0,15.7,1.5,21.1,3.5V440.1z M206.5,382.3c-11.9,0-20.6,1.9-28.7,4.9v18.5c8.2-3.2,15.7-5.3,25.8-5.3
20 | c14.6,0,22.6,6.7,22.6,18.9v2.2c-7.1-2.2-14.3-3.7-25.4-3.7c-21.4,0-37.2,9.4-37.2,28.5v0.3c0,17.8,15.3,27.3,32.7,27.3
21 | c13.9,0,23.5-5.5,29.8-12.7v10.9h20.9v-52.5C246.8,396,233.6,382.3,206.5,382.3L206.5,382.3z"/>
22 | </svg>
23 |
```
--------------------------------------------------------------------------------
/postfixadmin/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Postfix Admin?
2 |
3 | Postfix Admin is a web based interface to configure and manage a Postfix based email server for many users. Features include support for virtual domains and aliases, quotas, and vacation/out-of-the-office messages. It requires PHP, Postfix and one of MySQL, PostgreSQL or SQLite.
4 |
5 | %%LOGO%%
6 |
7 | # How to use this image
8 |
9 | ## No config.local.php / no existing setup
10 |
11 | If you do not have a config.local.php, then we fall back to look for environment variables to generate one.
12 |
13 | ```console
14 | $ docker run -e POSTFIXADMIN_DB_TYPE=mysqli \
15 | -e POSTFIXADMIN_DB_HOST=whatever \
16 | -e POSTFIXADMIN_DB_USER=user \
17 | -e POSTFIXADMIN_DB_PASSWORD=topsecret \
18 | -e POSTFIXADMIN_DB_NAME=postfixadmin \
19 | --name some-%%REPO%% \
20 | %%IMAGE%%
21 | ```
22 |
23 | `POSTFIXADMIN_DB_TYPE` can be one of :
24 |
25 | - mysqli
26 | - pgsql
27 | - sqlite
28 |
29 | Note: An SQLite database is not recommend but used as a fallback if you do not have a config.local.php and do not specify the above variables. Do not forget to add a volume for the SQLite path.
30 |
31 | You can also specify a `POSTFIXADMIN_SETUP_PASSWORD` environment variable.
32 |
33 | 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:
34 |
35 | ```console
36 | $ docker run -e POSTFIXADMIN_DB_TYPE=mysqli \
37 | -e POSTFIXADMIN_DB_HOST=whatever \
38 | -e POSTFIXADMIN_DB_USER=user \
39 | -e POSTFIXADMIN_DB_PASSWORD=topsecret \
40 | -e POSTFIXADMIN_DB_NAME=postfixadmin \
41 | --name some-%%REPO%% \
42 | -p 8080:80
43 | %%IMAGE%%
44 | ```
45 |
46 | Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browser.
47 |
48 | ## Existing config.local.php
49 |
50 | ```console
51 | $ docker run -v /local/path/to/config.local.php:/var/www/html/config.local.php \
52 | --name some-%%REPO%% \
53 | -p 8080:80 \
54 | %%IMAGE%%
55 | ```
56 |
57 | %%COMPOSE%%
58 |
59 | Run `docker compose up`, wait for it to initialize completely, and visit `http://localhost:8080` or `http://host-ip:8080` (as appropriate).
60 |
```
--------------------------------------------------------------------------------
/kibana/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Kibana?
2 |
3 | Kibana is an open source analytics and visualization platform designed to work with Elasticsearch. You use Kibana to search, view, and interact with data stored in Elasticsearch indices. You can easily perform advanced data analysis and visualize your data in a variety of charts, tables, and maps.
4 |
5 | > For more information about Kibana, please visit [www.elastic.co/products/kibana](https://www.elastic.co/products/kibana)
6 |
7 | %%LOGO%%
8 |
9 | # About This Image
10 |
11 | This default distribution is governed by the Elastic License, and includes the [full set of free features](https://www.elastic.co/subscriptions).
12 |
13 | View the detailed release notes [here](https://www.elastic.co/guide/en/kibana/current/release-notes.html).
14 |
15 | Not the version you're looking for? View all supported [past releases](https://www.docker.elastic.co).
16 |
17 | # How to use this image
18 |
19 | **Note:** Pulling an images requires using a specific version number tag. The `latest` tag is not supported.
20 |
21 | For Kibana versions prior to 6.4.0 a full list of images, tags, and documentation can be found at [docker.elastic.co](https://www.docker.elastic.co/).
22 |
23 | For full Kibana documentation see [here](https://www.elastic.co/guide/en/kibana/index.html).
24 |
25 | ## Running in Development Mode
26 |
27 | In the given example, Kibana will a attach to a user defined network (useful for connecting to other services (e.g. Elasticsearch)). If network has not yet been created, this can be done with the following command:
28 |
29 | ```console
30 | $ docker network create somenetwork
31 | ```
32 |
33 | *Note: In this example, Kibana is using the default configuration and expects to connect to a running Elasticsearch instance at http://localhost:9200*
34 |
35 | Run Kibana
36 |
37 | ```console
38 | $ docker run -d --name kibana --net somenetwork -p 5601:5601 kibana:tag
39 | ```
40 |
41 | Kibana can be accessed by browser via `http://localhost:5601` or `http://host-ip:5601`
42 |
43 | ## Running in Production Mode
44 |
45 | For additional information on running and configuring Kibana on Docker, see [Running Kibana on Docker](https://www.elastic.co/guide/en/kibana/current/docker.html)
46 |
```
--------------------------------------------------------------------------------
/jruby/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is JRuby?
2 |
3 | JRuby (http://www.jruby.org) is an implementation of Ruby (http://www.ruby-lang.org) on the JVM.
4 |
5 | Ruby is a dynamic, reflective, object-oriented, general-purpose, open-source programming language. According to its authors, Ruby was influenced by Perl, Smalltalk, Eiffel, Ada, and Lisp. It supports multiple programming paradigms, including functional, object-oriented, and imperative. It also has a dynamic type system and automatic memory management.
6 |
7 | > [wikipedia.org/wiki/Ruby_(programming_language)](https://en.wikipedia.org/wiki/Ruby_%28programming_language%29)
8 |
9 | JRuby leverages the robustness and speed of the JVM while providing the same Ruby that you already know and love. With JRuby you are able to take advantage of real native threads, enhanced garbage collection, and even import and use java libraries.
10 |
11 | %%LOGO%%
12 |
13 | # How to use this image
14 |
15 | ## Create a `Dockerfile` in your Ruby app project
16 |
17 | ```dockerfile
18 | FROM %%IMAGE%%:9
19 |
20 | # throw errors if Gemfile has been modified since Gemfile.lock
21 | RUN bundle config --global frozen 1
22 |
23 | WORKDIR /usr/src/app
24 |
25 | COPY Gemfile Gemfile.lock ./
26 | RUN bundle install
27 |
28 | COPY . .
29 |
30 | CMD ["./your-daemon-or-script.rb"]
31 | ```
32 |
33 | Put this file in the root of your app, next to the `Gemfile`.
34 |
35 | You can then build and run the Ruby image:
36 |
37 | ```console
38 | $ docker build -t my-ruby-app .
39 | $ docker run -it --name my-running-script my-ruby-app
40 | ```
41 |
42 | ### Generate a `Gemfile.lock`
43 |
44 | The above example `Dockerfile` expects a `Gemfile.lock` in your app directory. This `docker run` will help you generate one. Run it in the root of your app, next to the `Gemfile`:
45 |
46 | ```console
47 | $ docker run --rm -v "$PWD":/usr/src/app -w /usr/src/app %%IMAGE%%:9 bundle install --system
48 | ```
49 |
50 | ## Run a single Ruby script
51 |
52 | For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Ruby script by using the Ruby Docker image directly:
53 |
54 | ```console
55 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:9 jruby your-daemon-or-script.rb
56 | ```
57 |
```
--------------------------------------------------------------------------------
/eclipse-mosquitto/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Eclipse Mosquitto?
2 |
3 | Eclipse Mosquitto is an open source implementation of a server for versions 5, 3.1.1, and 3.1 of the MQTT protocol. Main homepage: http://mosquitto.org/
4 |
5 | %%LOGO%%
6 |
7 | # Eclipse Mosquitto and Cedalo
8 |
9 | [Cedalo](https://cedalo.com/?utm_source=docker-mosquitto&utm_medium=text&utm_campaign=cedalo-name) provides commercial support, enterprise MQTT products, professional services and training for Eclipse Mosquitto.
10 |
11 | # How to use this image
12 |
13 | ## Directories
14 |
15 | Three directories have been created in the image to be used for configuration, persistent storage and logs.
16 |
17 | /mosquitto/config
18 | /mosquitto/data
19 | /mosquitto/log
20 |
21 | It is suggested to mirror this structure for your local configuration.
22 |
23 | ## Configuration
24 |
25 | When running the image, the default configuration values are used. To use a custom configuration file, create your mosquitto.conf in `$PWD/mosquitto/config/mosquitto.conf`, then mount the config directory to `/mosquitto/config`.
26 |
27 | ```console
28 | $ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" %%IMAGE%%
29 | ```
30 |
31 | Configuration can be changed to:
32 |
33 | - persist data to `/mosquitto/data`
34 | - log to `/mosquitto/log/mosquitto.log`
35 |
36 | i.e. add the following to `mosquitto.conf`:
37 |
38 | persistence true
39 | persistence_location /mosquitto/data/
40 | log_dest file /mosquitto/log/mosquitto.log
41 |
42 | **Note**: If a volume is used, the data will persist between containers.
43 |
44 | ## Run
45 |
46 | Run a container using the new image:
47 |
48 | ```console
49 | $ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v /mosquitto/data -v /mosquitto/log %%IMAGE%%
50 | ```
51 |
52 | or:
53 |
54 | ```console
55 | $ docker run -it -p 1883:1883 -v "$PWD/mosquitto/config:/mosquitto/config" -v "$PWD/mosquitto/data:/mosquitto/data" -v "$PWD/mosquitto/log:/mosquitto/log" %%IMAGE%%
56 | ```
57 |
58 | **Note**: if the mosquitto configuration (mosquitto.conf) was modified to use non-default ports, the docker run command will need to be updated to expose the ports that have been configured.
59 |
60 | For example, if you use port 1883 and port 8080:
61 |
62 | ```console
63 | $ docker run -it -p 1883:1883 -p 8080:8080 -v "$PWD/mosquitto/config:/mosquitto/config" %%IMAGE%%
64 | ```
65 |
```
--------------------------------------------------------------------------------
/tomcat/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Tomcat?
2 |
3 | Apache Tomcat (or simply Tomcat) is an open source web server and servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Oracle, and provides a "pure Java" HTTP web server environment for Java code to run in. In the simplest config Tomcat runs in a single operating system process. The process runs a Java virtual machine (JVM). Every single HTTP request from a browser to Tomcat is processed in the Tomcat process in a separate thread.
4 |
5 | > [wikipedia.org/wiki/Apache_Tomcat](https://en.wikipedia.org/wiki/Apache_Tomcat)
6 |
7 | %%LOGO%% Logo © Apache Software Fountation
8 |
9 | # How to use this image.
10 |
11 | **Note:** as of [docker-library/tomcat#181](https://github.com/docker-library/tomcat/pull/181), the upstream-provided (example) webapps are *not* enabled by default, per [upstream's security recommendations](https://tomcat.apache.org/tomcat-9.0-doc/security-howto.html#Default_web_applications), but are still available under the `webapps.dist` folder within the image to make them easier to re-enable.
12 |
13 | Run the default Tomcat server (`CMD ["catalina.sh", "run"]`):
14 |
15 | ```console
16 | $ docker run -it --rm %%IMAGE%%:9.0
17 | ```
18 |
19 | You can test it by visiting `http://container-ip:8080` in a browser or, if you need access outside the host, on port 8888:
20 |
21 | ```console
22 | $ docker run -it --rm -p 8888:8080 %%IMAGE%%:9.0
23 | ```
24 |
25 | You can then go to `http://localhost:8888` or `http://host-ip:8888` in a browser (noting that it will return a 404 since there are no webapps loaded by default).
26 |
27 | The default Tomcat environment in the image is:
28 |
29 | CATALINA_BASE: /usr/local/tomcat
30 | CATALINA_HOME: /usr/local/tomcat
31 | CATALINA_TMPDIR: /usr/local/tomcat/temp
32 | JRE_HOME: /usr
33 | CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar
34 |
35 | The configuration files are available in `/usr/local/tomcat/conf/`. By default, no user is included in the "manager-gui" role required to operate the "/manager/html" web application. If you wish to use this app, you must define such a user in `tomcat-users.xml`.
36 |
```
--------------------------------------------------------------------------------
/chronograf/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # Chronograf
2 |
3 | Chronograf is InfluxData's open source web application. Use Chronograf with the other components of the [TICK](https://www.influxdata.com/products/) stack for infrastructure monitoring, alert management, data visualization, and database management.
4 |
5 | %%LOGO%%
6 |
7 | ## Using this image
8 |
9 | ### Running the container
10 |
11 | Chronograf runs on port 8888. It can be run and accessed by exposing that port:
12 |
13 | ```console
14 | $ docker run -p 8888:8888 %%IMAGE%%
15 | ```
16 |
17 | ### Mounting a volume
18 |
19 | The Chronograf image exposes a shared volume under `/var/lib/chronograf`, so you can mount a host directory to that point to access persisted container data. A typical invocation of the container might be:
20 |
21 | ```console
22 | $ docker run -p 8888:8888 \
23 | -v $PWD:/var/lib/chronograf \
24 | %%IMAGE%%
25 | ```
26 |
27 | Modify `$PWD` to the directory where you want to store data associated with the InfluxDB container.
28 |
29 | You can also have Docker control the volume mountpoint by using a named volume.
30 |
31 | ```console
32 | $ docker run -p 8888:8888 \
33 | -v chronograf:/var/lib/chronograf \
34 | %%IMAGE%%
35 | ```
36 |
37 | ### Using the container with InfluxDB
38 |
39 | The instructions here are very similar to the instructions when using `telegraf` with `influxdb`. These examples assume you are using Docker's built-in service discovery capability. In order to do so, we'll first create a new network:
40 |
41 | ```console
42 | $ docker network create influxdb
43 | ```
44 |
45 | Next, we'll start our InfluxDB container named `influxdb`:
46 |
47 | ```console
48 | $ docker run -d --name=influxdb \
49 | --net=influxdb \
50 | influxdb
51 | ```
52 |
53 | We can now start a Chronograf container that references this database.
54 |
55 | ```console
56 | $ docker run -p 8888:8888 \
57 | --net=influxdb \
58 | %%IMAGE%% --influxdb-url=http://influxdb:8086
59 | ```
60 |
61 | Try combining this with Telegraf to get dashboards for your infrastructure within minutes!
62 |
63 | #### Running as root
64 |
65 | Starting in v1.10.5, Chronograf no longer run as the root user by default. If a user wants to revert this change they can set `CHRONOGRAF_AS_ROOT=true` as an environment variable.
66 |
67 | ## Official Documentation
68 |
69 | See the [official docs](https://docs.influxdata.com/chronograf/latest/) for information on creating visualizations.
70 |
```
--------------------------------------------------------------------------------
/alt/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # ALT Linux
2 |
3 | This image serves as the `official ALT image` for the [ALT Linux](https://altlinux.org/).
4 |
5 | %%LOGO%%
6 |
7 | # ALT Linux Team
8 |
9 | [ALT Linux Team](http://www.altlinux.org/ALT_Linux_Team) is an international community numbering over 200 free software developers.
10 |
11 | # Sisyphus
12 |
13 | [Sisyphus](https://packages.altlinux.org/ru/Sisyphus/home) is a daily updated repository which serves as a basis for all ALT distributions. Sisyphus integrity supported by the ALT Linux Team, the original software packaging technology, and apt-get (apt-rpm) utility allows users to easily update the system and be aware of any news on the free software. This daily updated repository contains the latest software with all its benefits and pitfalls (latent sometimes).
14 |
15 | The name Sisyphus comes from the Greek mythology. Uninterrupted efforts on improvement of technologies set in the repository make ALT Linux Team similar to tireless Sisyphus continuously rolling stones up the hill.
16 |
17 | # About Platform 9
18 |
19 | As said above, Sisyphus is a frequently updated repository mainly designed for developers. Stable distributions by ALT are the best solution for those users preferring stability and predictability of the system to its functionality (primarily new and corporate users). Such stable distributions are based on stable Sisyphus repository slices called platforms. Platform 9 (p9) was created in June, 2019, and will be supported till December, 2022.
20 |
21 | # About this image
22 |
23 | The `%%IMAGE%%:latest` tag will always point the latest stable release (which is, at the time of this writing, `%%IMAGE%%:p9`).
24 |
25 | ## How It's Made
26 |
27 | This image was created with the help of mkimage and hasher tools.
28 |
29 | [Mkimage](https://en.altlinux.org/Mkimage) is a tool used to create images with Linux kernel from the set Sisyphus-like repository. Mkimage uses a set of Makefiles and shell hooks.
30 |
31 | [Hasher](https://en.altlinux.org/Hasher) is a tool used for safe and repeatable packaging in clean and controllable environment. This is achieved through creation of a minimum build environment in chroot, installation of all necessary packaging dependencies there, and packet assembly in the new environment. Every package requires a new build environment.
32 |
```
--------------------------------------------------------------------------------
/spiped/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # spiped
2 |
3 | ## What is spiped?
4 |
5 | Spiped (pronounced "ess-pipe-dee") is a utility for creating symmetrically encrypted and authenticated pipes between socket addresses, so that one may connect to one address (e.g., a UNIX socket on localhost) and transparently have a connection established to another address (e.g., a UNIX socket on a different system). This is similar to `ssh -L` functionality, but does not use SSH and requires a pre-shared symmetric key.
6 |
7 | > [tarsnap.com/spiped.html](https://www.tarsnap.com/spiped.html)
8 |
9 | ## How to use this image
10 |
11 | This image automatically takes the key from the `/spiped/key` file (`-k`) and runs spiped in foreground (`-F`). Other than that it takes the same options *spiped* itself does. You can list the available flags by running the image without arguments:
12 |
13 | ```console
14 | $ docker run -it --rm %%IMAGE%%
15 | usage: spiped {-e | -d} -s <source socket> -t <target socket> -k <key file>
16 | [-DFj] [-f | -g] [-n <max # connections>] [-o <connection timeout>]
17 | [-p <pidfile>] [-r <rtime> | -R]
18 | ```
19 |
20 | For example running spiped to take encrypted connections on port 8025 and forward them to port 25 on localhost would look like this:
21 |
22 | ```console
23 | $ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 8025:8025 --init %%IMAGE%% -d -s '[0.0.0.0]:8025' -t '[127.0.0.1]:25'
24 | ```
25 |
26 | Usually you would combine this image with another linked container. The following example would take encrypted connections on port 9200 and forward them to port 9200 in the container with the name `elasticsearch`:
27 |
28 | ```console
29 | $ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 9200:9200 --link elasticsearch:elasticsearch --init %%IMAGE%% -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
30 | ```
31 |
32 | If you don't need any to bind to a privileged port you can pass `--user spiped` to make *spiped* run as an unprivileged user:
33 |
34 | ```console
35 | $ docker run -d -v /path/to/keyfile:/spiped/key:ro --user spiped -p 9200:9200 --link elasticsearch:elasticsearch --init %%IMAGE%% -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
36 | ```
37 |
38 | ### Generating a key
39 |
40 | You can save a new keyfile named `spiped-keyfile` to the folder `/path/to/keyfile/` by running:
41 |
42 | ```console
43 | $ docker run -it --rm -v /path/to/keyfile:/spiped/key %%IMAGE%% spiped-generate-key.sh
44 | ```
45 |
46 | Afterwards transmit `spiped-keyfile` securely to another host (e.g. by using scp).
47 |
```
--------------------------------------------------------------------------------
/unit/logo.svg:
--------------------------------------------------------------------------------
```
1 | <svg xmlns="http://www.w3.org/2000/svg" viewBox="149 203 988 357"><defs><style>.cls-1{fill:#fff;}.cls-2{fill:#232221;}.cls-3{fill:#009639;}</style></defs><g><path class="cls-2" d="M567.73,295.24h0a11.09,11.09,0,0,1,11.09,11.09v92.81q0,26.76,10,40T622,452.41q23.38,0,33-13.38t9.64-39.89V306.33a11.09,11.09,0,0,1,11.09-11.09h0a11.09,11.09,0,0,1,11.09,11.09v92.81q0,19.29-4.46,32.9t-12.78,22.54a48.69,48.69,0,0,1-20.49,13,85.46,85.46,0,0,1-27.36,4.1q-31.1,0-48.09-17.35t-17-56.17V306.33A11.09,11.09,0,0,1,567.73,295.24Z"/><path class="cls-2" d="M730.45,342.72h0a10.37,10.37,0,0,1,10.37,10.37v8.68q9.16-12.3,20.25-17.6a53.53,53.53,0,0,1,23.38-5.3q21.21,0,31.46,11.57t10.24,34v72.44a10.49,10.49,0,0,1-10.49,10.49h0a10.49,10.49,0,0,1-10.49-10.49V388.53q0-17.35-6.27-24.47t-19.28-7.11a41.64,41.64,0,0,0-13.86,2.41,34.27,34.27,0,0,0-12.42,7.71,40.21,40.21,0,0,0-9.16,11.21q-3.13,5.9-3.13,15.31v63.28a10.49,10.49,0,0,1-10.49,10.49h0a10.49,10.49,0,0,1-10.49-10.49V353.09A10.37,10.37,0,0,1,730.45,342.72Z"/><path class="cls-2" d="M868.45,295.24h0a11.21,11.21,0,0,1,11.21,11.21v1.93a11.21,11.21,0,0,1-11.21,11.21h0a11.21,11.21,0,0,1-11.21-11.21v-1.93A11.21,11.21,0,0,1,868.45,295.24Zm0,47.49h0a10.49,10.49,0,0,1,10.49,10.49V456.87a10.49,10.49,0,0,1-10.49,10.49h0A10.49,10.49,0,0,1,858,456.87V353.21A10.49,10.49,0,0,1,868.45,342.72Z"/><path class="cls-2" d="M919,359.36H908a8.32,8.32,0,0,1-8.32-8.32h0a8.32,8.32,0,0,1,8.32-8.32h11v-23.5a10.49,10.49,0,0,1,10.49-10.49h0a10.49,10.49,0,0,1,10.49,10.49v23.5h24.71A8.32,8.32,0,0,1,973,351h0a8.32,8.32,0,0,1-8.32,8.32H939.92v73q0,9.16,4.1,14.7t12.53,5.55a70,70,0,0,0,8.78-1,8.54,8.54,0,0,1,9.69,6.59h0a8.58,8.58,0,0,1-6.54,10.26l-2.17.44A72.17,72.17,0,0,1,952.94,470q-10.61,0-17.12-3.13A25.43,25.43,0,0,1,925.46,458a34.65,34.65,0,0,1-5.18-13.74A105.37,105.37,0,0,1,919,426.86Z"/><path class="cls-3" d="M452.69,284.92,317.13,206.65a21.46,21.46,0,0,0-21.4,0L160.17,284.92a21.46,21.46,0,0,0-10.69,18.53V460a21.45,21.45,0,0,0,10.7,18.53l135.56,78.26a21.46,21.46,0,0,0,21.4,0l135.56-78.26A21.45,21.45,0,0,0,463.39,460V303.45A21.45,21.45,0,0,0,452.69,284.92Z"/><path class="cls-1" d="M384.85,441.92c0,9.29-8.21,17-19.84,17-8.33,0-17.94-3.36-23.81-10.65l-78.27-93.67v87.34a17,17,0,0,1-17,17h-1a17,17,0,0,1-17-17l0-120.42c0-9.29,8.21-17,19.84-17,8.33,0,17.94,3.36,23.81,10.65l78.27,93.67V321.51a17,17,0,0,1,17-17h1a17,17,0,0,1,17,17Z"/></g></svg>
2 |
```
--------------------------------------------------------------------------------
/emqx/logo.svg:
--------------------------------------------------------------------------------
```
1 | <?xml version="1.0" encoding="UTF-8"?>
2 | <svg width="320px" height="320px" viewBox="0 0 320 320" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
3 | <title>320备份</title>
4 | <g id="320备份" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
5 | <g id="编组-2备份-17" transform="translate(40.000000, 22.000000)" fill="#00B173">
6 | <g id="编组" transform="translate(41.424725, 85.086839)">
7 | <path d="M133.374826,0 L31.0713227,0 L31.0713227,0.0212798466 C30.9290586,0.0148958926 30.7889285,0 30.6459532,0 C25.3352361,0 21.0303258,4.29285438 21.0303258,9.58869887 C21.0303258,14.883834 25.3352361,19.1766884 30.6459532,19.1766884 C30.7889285,19.1766884 30.9290586,19.1617925 31.0713227,19.1554086 L31.0713227,19.1766884 L133.374826,19.1766884 C138.684831,19.1766884 142.990453,14.883834 142.990453,9.58869887 C142.990453,4.29285438 138.684831,0 133.374826,0" id="Fill-4"></path>
8 | <path d="M133.374826,91.3398402 L31.0713227,91.3398402 L31.0713227,91.3604107 C30.9290586,91.354736 30.7889285,91.3398402 30.6459532,91.3398402 C25.3352361,91.3398402 21.0303258,95.6326945 21.0303258,100.928539 C21.0303258,106.222965 25.3352361,110.515819 30.6459532,110.515819 C30.7889285,110.515819 30.9290586,110.501633 31.0713227,110.495249 L31.0713227,110.515819 L133.374826,110.515819 C138.684831,110.515819 142.990453,106.222965 142.990453,100.928539 C142.990453,95.6326945 138.684831,91.3398402 133.374826,91.3398402" id="Fill-6"></path>
9 | <path d="M106.49887,55.2582997 C106.49887,50.2582451 102.659163,46.1569094 97.7603004,45.7135792 L97.7603004,45.6696009 L10.0409968,45.6696009 L10.0409968,45.6908807 C9.89873278,45.6852061 9.75931401,45.6696009 9.61562732,45.6696009 C4.30491023,45.6696009 0,49.9624553 0,55.2582997 C0,60.5541442 4.30491023,64.8469986 9.61562732,64.8469986 C9.75931401,64.8469986 9.89873278,64.8313934 10.0409968,64.8250094 L10.0409968,64.8469986 L97.7603004,64.8469986 L97.7603004,64.8023109 C102.659163,64.3596901 106.49887,60.2583544 106.49887,55.2582997" id="Fill-8"></path>
10 | </g>
11 | <path d="M240,69.25 L120,0 L0,69.25 L0,207.75 L120,277 L240,207.75 L240,69.25 Z M120,20.7115288 L222.048512,79.6057644 L222.048512,197.381421 L120,256.275657 L17.9386675,197.381421 L17.9386675,79.6057644 L120,20.7115288 Z" id="多边形" fill-rule="nonzero"></path>
12 | </g>
13 | </g>
14 | </svg>
```
--------------------------------------------------------------------------------
/matomo/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # Matomo (formerly Piwik)
2 |
3 | [Matomo](https://matomo.org/) (formerly Piwik) is the leading open-source analytics platform that gives you more than just powerful analytics:
4 |
5 | - Free open-source software
6 | - 100% data ownership
7 | - User privacy protection
8 | - User-centric insights
9 | - Customisable and extensible
10 |
11 | %%LOGO%%
12 |
13 | # How to use this image
14 |
15 | You can run the Matomo container and service like so:
16 |
17 | ```bash
18 | docker run -d --link some-mysql:db %%IMAGE%%
19 | ```
20 |
21 | This assumes you've already launched a suitable MySQL or MariaDB database container.
22 |
23 | ## Persistent data
24 |
25 | Use a Docker volume to keep persistent data:
26 |
27 | ```bash
28 | docker run -d -p 8080:80 --link some-mysql:db -v matomo:/var/www/html %%IMAGE%%
29 | ```
30 |
31 | ## Matomo Installation
32 |
33 | Once you're up and running, you'll arrive at the configuration wizard page. If you're using the compose file, at the `Database Setup` step, please enter the following:
34 |
35 | - Database Server: `db`
36 | - Login: MYSQL_USER
37 | - Password: MYSQL_PASSWORD
38 | - Database Name: MYSQL_DATABASE
39 |
40 | And leave the rest as default.
41 |
42 | Then you can continue the installation with the super user.
43 |
44 | The following environment variables are also honored for configuring your Matomo instance:
45 |
46 | - `MATOMO_DATABASE_HOST`
47 | - `MATOMO_DATABASE_ADAPTER`
48 | - `MATOMO_DATABASE_TABLES_PREFIX`
49 | - `MATOMO_DATABASE_USERNAME`
50 | - `MATOMO_DATABASE_PASSWORD`
51 | - `MATOMO_DATABASE_DBNAME`
52 |
53 | The PHP memory limit can be configured with the following environment variable:
54 |
55 | - `PHP_MEMORY_LIMIT`
56 |
57 | ## Docker Compose examples and log import instructions
58 |
59 | A minimal set-up using Docker Compose is available in the [.examples folder](%%GITHUB-REPO%%/tree/master/.examples).
60 |
61 | If you want to use the import logs script, you can then run the following container as needed, in order to execute the python import logs script:
62 |
63 | ```bash
64 | docker run --rm --volumes-from="matomo-app-1" --link matomo-app-1 python:3-alpine python /var/www/html/misc/log-analytics/import_logs.py --url=http://ip.of.your.matomo.example --login=yourlogin --password=yourpassword --idsite=1 --recorders=4 /var/www/html/logs/access.log
65 | ```
66 |
67 | ## Contribute
68 |
69 | Pull requests are very welcome!
70 |
71 | We'd love to hear your feedback and suggestions in the issue tracker: [%%ISSUES%%](%%ISSUES%%).
72 |
73 | ## GeoIP
74 |
75 | ~~This product includes GeoLite data created by MaxMind, available from [https://www.maxmind.com](https://www.maxmind.com).~~ https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/
76 |
```
--------------------------------------------------------------------------------
/bash/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Bash?
2 |
3 | Bash is the [GNU](http://www.gnu.org/) Project's Bourne Again SHell, a complete implementation of the [IEEE POSIX and Open Group shell specification](http://www.opengroup.org/onlinepubs/9699919799/nfindex.html) with interactive command line editing, job control on architectures that support it, csh-like features such as history substitution and brace expansion, and a slew of other features.
4 |
5 | > [tiswww.case.edu/php/chet/bash/bashtop.html](https://tiswww.case.edu/php/chet/bash/bashtop.html)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | The primary use cases this image is targeting are testing new features of more recent Bash versions before your primary distribution updates packages and testing shell scripts against different Bash versions to ensure compatibility. There are likely other interesting use cases as well, but those are the primary two the image was initially created to solve!
12 |
13 | ## Notes
14 |
15 | There are a few main things that are important to note regarding this image:
16 |
17 | 1. Bash itself is installed at `/usr/local/bin/bash`, not `/bin/bash`, so the recommended shebang is `#!/usr/bin/env bash`, not `#!/bin/bash` (or explicitly running your script via `bash /.../script.sh` instead of letting the shebang invoke Bash automatically). The image does not include `/bin/bash`, but if it is installed via the package manager included in the image, that package will install to `/bin/bash` and might cause confusion (although `/usr/local/bin` is ahead of `/bin` in `$PATH`, so as long as plain `bash` or `/usr/bin/env` are used consistently, the image-provided Bash will be preferred).
18 |
19 | 2. Bash is the only thing included, so if your scripts rely on external tools (such as `jq`, for example), those will need to be added manually (via `apk add --no-cache jq`, for example).
20 |
21 | ## Interactive shell
22 |
23 | ```console
24 | $ docker run -it --rm %%IMAGE%%:4.4
25 | bash-4.4# which bash
26 | /usr/local/bin/bash
27 | bash-4.4# echo $BASH_VERSION
28 | 4.4.0(1)-release
29 | ```
30 |
31 | ## Testing scripts via bind-mount
32 |
33 | ```console
34 | $ docker run -it --rm -v /path/to/script.sh:/script.sh:ro %%IMAGE%%:4.4 bash /script.sh
35 | ...
36 | $ docker run -it --rm -v /path/to/script.sh:/script.sh:ro %%IMAGE%%:3.2 bash /script.sh
37 | ...
38 | ```
39 |
40 | ## Testing scripts via `Dockerfile`
41 |
42 | ```dockerfile
43 | FROM %%IMAGE%%:4.4
44 |
45 | COPY script.sh /
46 |
47 | CMD ["bash", "/script.sh"]
48 | ```
49 |
50 | Then, build and run the Docker image:
51 |
52 | ```console
53 | $ docker build -t my-bash-app .
54 | ...
55 | $ docker run -it --rm --name my-running-app my-bash-app
56 | ...
57 | ```
58 |
```
--------------------------------------------------------------------------------
/rust/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Rust?
2 |
3 | Rust is a systems programming language sponsored by Mozilla Research. It is designed to be a "safe, concurrent, practical language", supporting functional and imperative-procedural paradigms. Rust is syntactically similar to C++, but is designed for better memory safety while maintaining performance.
4 |
5 | > [wikipedia.org/wiki/Rust_(programming_language)](https://en.wikipedia.org/wiki/Rust_%28programming_language%29)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Start a Rust instance running your app
12 |
13 | The most straightforward way to use this image is to use a Rust container as both the build and runtime environment. In your `Dockerfile`, writing something along the lines of the following will compile and run your project:
14 |
15 | ```dockerfile
16 | FROM %%IMAGE%%:1.67
17 |
18 | WORKDIR /usr/src/myapp
19 | COPY . .
20 |
21 | RUN cargo install --path .
22 |
23 | CMD ["myapp"]
24 | ```
25 |
26 | Then, build and run the Docker image:
27 |
28 | ```console
29 | $ docker build -t my-rust-app .
30 | $ docker run -it --rm --name my-running-app my-rust-app
31 | ```
32 |
33 | This creates an image that has all of the rust tooling for the image, which is 1.8gb. If you just want the compiled application:
34 |
35 | ```dockerfile
36 | FROM rust:1.67 as builder
37 | WORKDIR /usr/src/myapp
38 | COPY . .
39 | RUN cargo install --path .
40 |
41 | FROM debian:bullseye-slim
42 | RUN apt-get update && apt-get install -y extra-runtime-dependencies && rm -rf /var/lib/apt/lists/*
43 | COPY --from=builder /usr/local/cargo/bin/myapp /usr/local/bin/myapp
44 | CMD ["myapp"]
45 | ```
46 |
47 | Note: Some shared libraries may need to be installed as shown in the installation of the `extra-runtime-dependencies` line above.
48 |
49 | This method will create an image that is less than 200mb. If you switch to using the Alpine-based rust image, you might be able to save another 60mb.
50 |
51 | See https://docs.docker.com/develop/develop-images/multistage-build/ for more information.
52 |
53 | ## Compile your app inside the Docker container
54 |
55 | There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
56 |
57 | ```console
58 | $ docker run --rm --user "$(id -u)":"$(id -g)" -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:1.23.0 cargo build --release
59 | ```
60 |
61 | This will add your current directory, as a volume, to the container, set the working directory to the volume, and run the command `cargo build --release`. This tells Cargo, Rust's build system, to compile the crate in `myapp` and output the executable to `target/release/myapp`.
62 |
```
--------------------------------------------------------------------------------
/generate-repo-stub-readme.sh:
--------------------------------------------------------------------------------
```bash
1 | #!/usr/bin/env bash
2 | set -Eeuo pipefail
3 |
4 | cd "$(dirname "$(readlink -f "$BASH_SOURCE")")"
5 |
6 | repo="${1:-}"
7 |
8 | if [ -z "$repo" ]; then
9 | echo >&2 'error: no repo specified'
10 | cat >&2 <<EOUSAGE
11 | usage: $0 repo [> README.md]
12 | ie: $0 php > ../php/README.md
13 |
14 | This script generates a stub README to standard out for the specified repo.
15 | EOUSAGE
16 | exit 1
17 | fi
18 |
19 | gitRepo='https://github.com/docker-library/docs'
20 | hubPage="https://hub.docker.com/_/$repo/"
21 |
22 | canonicalRepo="https://github.com/docker-library/$repo"
23 | if [ -s "$repo/github-repo" ]; then
24 | canonicalRepo="$(< "$repo/github-repo")"
25 | fi
26 | canonicalRepo="$(curl -fsSLI -o /dev/null -w '%{url_effective}\n' "$canonicalRepo")" # follow redirects (http://stackoverflow.com/a/3077316/433558)
27 |
28 | maintainer="$(sed -e 's!%%GITHUB-REPO%%!'"$canonicalRepo"'!g' "$repo/maintainer.md")"
29 |
30 | if [ -f "$repo/deprecated.md" ]; then
31 | echo '# DEPRECATED'
32 | echo
33 | cat "$repo/deprecated.md"
34 | echo
35 | fi
36 |
37 | case "$repo" in
38 | buildpack-deps | docker | hello-world | hylang) disclaimer='' ;;
39 | *) disclaimer=" (not to be confused with any official \`$repo\` image provided by \`$repo\` upstream)" ;;
40 | esac
41 |
42 | cat <<EOREADME
43 | # $canonicalRepo
44 |
45 | ## Maintained by: $maintainer
46 |
47 | This is the Git repo of the [Docker "Official Image"](https://github.com/docker-library/official-images#what-are-official-images) for [\`$repo\`]($hubPage)$disclaimer. See [the Docker Hub page]($hubPage) for the full readme on how to use this Docker image and for information regarding contributing and issues.
48 |
49 | The [full image description on Docker Hub]($hubPage) is generated/maintained over in [the docker-library/docs repository]($gitRepo), specifically in [the \`$repo\` directory]($gitRepo/tree/master/$repo).
50 |
51 | ## See a change merged here that doesn't show up on Docker Hub yet?
52 |
53 | For more information about the full official images change lifecycle, see [the "An image's source changed in Git, now what?" FAQ entry](https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what).
54 |
55 | For outstanding \`$repo\` image PRs, check [PRs with the "library/$repo" label on the official-images repository](https://github.com/docker-library/official-images/labels/library%2F$repo). For the current "source of truth" for [\`$repo\`]($hubPage), see [the \`library/$repo\` file in the official-images repository](https://github.com/docker-library/official-images/blob/master/library/$repo).
56 |
57 | <!-- THIS FILE IS GENERATED BY $gitRepo/blob/master/generate-repo-stub-readme.sh -->
58 | EOREADME
59 |
```
--------------------------------------------------------------------------------
/python/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Python?
2 |
3 | Python is an interpreted, interactive, object-oriented, open-source programming language. It incorporates modules, exceptions, dynamic typing, very high level dynamic data types, and classes. Python combines remarkable power with very clear syntax. It has interfaces to many system calls and libraries, as well as to various window systems, and is extensible in C or C++. It is also usable as an extension language for applications that need a programmable interface. Finally, Python is portable: it runs on many Unix variants, on the Mac, and on Windows 2000 and later.
4 |
5 | > [wikipedia.org/wiki/Python_(programming_language)](https://en.wikipedia.org/wiki/Python_%28programming_language%29)
6 |
7 | %%LOGO%%
8 |
9 | # How to use this image
10 |
11 | ## Create a `Dockerfile` in your Python app project
12 |
13 | ```dockerfile
14 | FROM %%IMAGE%%:3
15 |
16 | WORKDIR /usr/src/app
17 |
18 | COPY requirements.txt ./
19 | RUN pip install --no-cache-dir -r requirements.txt
20 |
21 | COPY . .
22 |
23 | CMD [ "python", "./your-daemon-or-script.py" ]
24 | ```
25 |
26 | or (if you need to use Python 2):
27 |
28 | ```dockerfile
29 | FROM %%IMAGE%%:2
30 |
31 | WORKDIR /usr/src/app
32 |
33 | COPY requirements.txt ./
34 | RUN pip install --no-cache-dir -r requirements.txt
35 |
36 | COPY . .
37 |
38 | CMD [ "python", "./your-daemon-or-script.py" ]
39 | ```
40 |
41 | You can then build and run the Docker image:
42 |
43 | ```console
44 | $ docker build -t my-python-app .
45 | $ docker run -it --rm --name my-running-app my-python-app
46 | ```
47 |
48 | ## Run a single Python script
49 |
50 | For many simple, single file projects, you may find it inconvenient to write a complete `Dockerfile`. In such cases, you can run a Python script by using the Python Docker image directly:
51 |
52 | ```console
53 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:3 python your-daemon-or-script.py
54 | ```
55 |
56 | or (again, if you need to use Python 2):
57 |
58 | ```console
59 | $ docker run -it --rm --name my-running-script -v "$PWD":/usr/src/myapp -w /usr/src/myapp %%IMAGE%%:2 python your-daemon-or-script.py
60 | ```
61 |
62 | ## Multiple Python versions in the image
63 |
64 | In the non-slim variants there will be an additional (distro-provided) `python` executable at `/usr/bin/python` (and/or `/usr/bin/python3`) while the desired image-provided `/usr/local/bin/python` is the default choice in the `$PATH`. This is an unfortunate side-effect of using the `buildpack-deps` image in the non-slim variants (and many distribution-provided tools being written against and likely to break with a different Python installation, so we can't safely remove/overwrite it).
65 |
```
--------------------------------------------------------------------------------
/archlinux/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Arch Linux?
2 |
3 | Arch Linux, is a lightweight and flexible Linux® distribution that tries to Keep It Simple.
4 |
5 | Currently, we have official packages optimized for the x86-64 architecture. We complement our official package sets with a community-operated package repository that grows in size and quality each and every day.
6 |
7 | Our strong community is diverse and helpful, and we pride ourselves on the range of skill sets and uses for Arch that stem from it. Please check out our forums and mailing lists to get your feet wet. Also glance through our [wiki](https://wiki.archlinux.org) if you want to learn more about Arch.
8 |
9 | %%LOGO%%
10 |
11 | # About this image
12 |
13 | The root filesystem tarball for this image is auto-generated weekly at 00:00 UTC on Sunday in Arch Linux infrastructure. Given the rolling-release nature of Arch Linux, images are tagged with the included meta package and the timestamp of the date they were generated. For example, `%%IMAGE%%:base-20201101.0.7893` was generated the First of November 2020 in [CI job #7893](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/jobs/7893). The `latest` tag will always match the latest `base` tag.
14 |
15 | Besides `base` we also provide images for the `base-devel` and `multilib-devel` meta packages.
16 |
17 | This image is intended to serve the following goals:
18 |
19 | - Provide the Arch experience in a Docker Image
20 | - Provide simplest but complete image to `base`, `base-devel` and `multilib-devel` on a regular basis
21 | - `pacman` needs to work out of the box
22 | - All installed packages have to be kept unmodified
23 |
24 | > ⚠️⚠️⚠️ NOTE: For Security Reasons, these images strip the pacman lsign key. This is because the same key would be spread to all containers of the same image, allowing for malicious actors to inject packages (via, for example, a man-in-the-middle). In order to create a lsign-key run `pacman-key --init` on the first execution, but be careful to not redistribute that key. ⚠️⚠️⚠️
25 |
26 | ## Availability
27 |
28 | Root filesystem tarballs are [provided by our GitLab](https://gitlab.archlinux.org/archlinux/archlinux-docker/-/releases) for at least two months.
29 |
30 | ## Updating
31 |
32 | Arch Linux is a rolling release distribution, so a full update is recommended when installing new packages. In other words, we suggest to either execute `RUN pacman -Syu` immediately after your `FROM` statement or as soon as you `docker run` into a container.
33 |
34 | ## How It's Made
35 |
36 | You can build this image with the tools on the [Arch Linux GitLab repository](https://gitlab.archlinux.org/archlinux/archlinux-docker) using the included makefile.
37 |
```
--------------------------------------------------------------------------------
/plone/logo.svg:
--------------------------------------------------------------------------------
```
1 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
2 | <!-- Generator: Adobe Illustrator 13.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 14948) -->
3 |
4 | <svg
5 | xmlns:dc="http://purl.org/dc/elements/1.1/"
6 | xmlns:cc="http://creativecommons.org/ns#"
7 | xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
8 | xmlns:svg="http://www.w3.org/2000/svg"
9 | xmlns="http://www.w3.org/2000/svg"
10 | xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
11 | xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
12 | version="1.1"
13 | id="Layer_1"
14 | x="0px"
15 | y="0px"
16 | width="40.686001"
17 | height="40.686001"
18 | viewBox="0 0 40.685999 40.686"
19 | enable-background="new 0 0 158.253 40.686"
20 | xml:space="preserve"
21 | sodipodi:docname="logo.svg"
22 | inkscape:version="0.92.2 2405546, 2018-03-11"><metadata
23 | id="metadata3880"><rdf:RDF><cc:Work
24 | rdf:about=""><dc:format>image/svg+xml</dc:format><dc:type
25 | rdf:resource="http://purl.org/dc/dcmitype/StillImage" /><dc:title></dc:title></cc:Work></rdf:RDF></metadata><defs
26 | id="defs3878" /><sodipodi:namedview
27 | pagecolor="#ffffff"
28 | bordercolor="#666666"
29 | borderopacity="1"
30 | objecttolerance="10"
31 | gridtolerance="10"
32 | guidetolerance="10"
33 | inkscape:pageopacity="0"
34 | inkscape:pageshadow="2"
35 | inkscape:window-width="1916"
36 | inkscape:window-height="1048"
37 | id="namedview3876"
38 | showgrid="false"
39 | inkscape:snap-page="true"
40 | inkscape:zoom="6.5464791"
41 | inkscape:cx="69.00927"
42 | inkscape:cy="-3.8796729"
43 | inkscape:window-x="0"
44 | inkscape:window-y="14"
45 | inkscape:window-maximized="0"
46 | inkscape:current-layer="Layer_1" />
47 |
48 |
49 |
50 |
51 |
52 | <circle
53 | cx="17.716999"
54 | cy="11.560999"
55 | r="4.402"
56 | id="circle3857"
57 | style="fill:#009ddc" />
58 | <path
59 | d="m 31.069,20.355999 c 0,2.433 -1.969,4.401 -4.403,4.401 -2.427,0 -4.401,-1.97 -4.401,-4.401 0,-2.433 1.975,-4.401 4.401,-4.401 2.435,-0.001 4.403,1.969 4.403,4.401 z"
60 | id="path3859"
61 | inkscape:connector-curvature="0"
62 | style="fill:#009ddc" />
63 | <circle
64 | cx="17.702"
65 | cy="29.176001"
66 | r="4.402"
67 | id="circle3861"
68 | style="fill:#009ddc" />
69 | <g
70 | id="g3865">
71 | <path
72 | d="M 20.343,0 C 9.108,0.001 0.001,9.108 0,20.343 0.001,31.577 9.108,40.684 20.343,40.686 31.578,40.684 40.684,31.579 40.686,20.343 40.684,9.108 31.578,0.001 20.343,0 Z M 31.792,31.792 C 28.855,34.726 24.82,36.534 20.342,36.535 15.864,36.534 11.829,34.724 8.892,31.792 5.959,28.855 4.151,24.82 4.15,20.343 4.151,15.865 5.959,11.83 8.893,8.893 11.83,5.959 15.865,4.151 20.343,4.15 c 4.478,10e-4 8.513,1.81 11.45,4.743 2.934,2.938 4.742,6.973 4.743,11.45 -0.002,4.477 -1.81,8.512 -4.744,11.449 z"
73 | id="path3863"
74 | inkscape:connector-curvature="0"
75 | style="fill:#009ddc" />
76 | </g>
77 |
78 |
79 | </svg>
```
--------------------------------------------------------------------------------
/dart/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # What is Dart?
2 |
3 | Dart is a client-optimized language for developing fast apps on any platform. Its goal is to offer the most productive programming language for multi-platform development, paired with a flexible execution runtime platform for app frameworks. For more details, see https://dart.dev.
4 |
5 | By utilizing Dart's support for ahead-of-time (AOT) [compilation to executables](https://dart.dev/tools/dart-compile#exe), you can create very small runtime images (~10 MB).
6 |
7 | ## Using this image
8 |
9 | We recommend using small runtime images that leverage Dart's support for ahead-of-time (AOT) [compilation to executables](https://dart.dev/tools/dart-compile#exe). This enables creating small runtime images (~10 MB).
10 |
11 | ### Creating a Dart server app
12 |
13 | After [installing](https://dart.dev/get-dart) the Dart SDK, version 2.14 or later, use the `dart` command to create a new server app:
14 |
15 | ```shell
16 | $ dart create -t server-shelf myserver
17 | ```
18 |
19 | ### Running the server with Docker Desktop
20 |
21 | If you have [Docker Desktop](https://www.docker.com/get-started) installed, you can build and run on your machine with the `docker` command:
22 |
23 | ```shell
24 | $ docker build -t dart-server .
25 | $ docker run -it --rm -p 8080:8080 --name myserver dart-server
26 | ```
27 |
28 | When finished, you can stop the container using the name you provided:
29 |
30 | ```shell
31 | $ docker kill myserver
32 | ```
33 |
34 | ## Image documentation
35 |
36 | ### `Dockerfile`
37 |
38 | The `Dockerfile` created by the `dart` tool performs two steps:
39 |
40 | 1. Using the Dart SDK in the `dart:stable` image, compiles your server (`bin/server.dart`) to an executable (`server`).
41 |
42 | 2. Assembles the runtime image by combining the compiled server with the Dart VM runtime and it's needed dependencies located in `/runtime/`.
43 |
44 | ```Dockerfile
45 | # Specify the Dart SDK base image version using dart:<version> (ex: dart:2.12)
46 | FROM dart:stable AS build
47 |
48 | # Resolve app dependencies.
49 | WORKDIR /app
50 | COPY pubspec.* ./
51 | RUN dart pub get
52 |
53 | # Copy app source code and AOT compile it.
54 | COPY . .
55 | # Ensure packages are still up-to-date if anything has changed
56 | RUN dart pub get --offline
57 | RUN dart compile exe bin/server.dart -o bin/server
58 |
59 | # Build minimal serving image from AOT-compiled `/server` and required system
60 | # libraries and configuration files stored in `/runtime/` from the build stage.
61 | FROM scratch
62 | COPY --from=build /runtime/ /
63 | COPY --from=build /app/bin/server /app/bin/
64 |
65 | # Start server.
66 | EXPOSE 8080
67 | CMD ["/app/bin/server"]
68 | ```
69 |
70 | ### `.dockerignore`
71 |
72 | Additionally it creates a recommended `.dockerignore` file, which enumarates files that should be omitted from the built Docker image:
73 |
74 | ```text
75 | .dockerignore
76 | Dockerfile
77 | build/
78 | .dart_tool/
79 | .git/
80 | .github/
81 | .gitignore
82 | .packages
83 | ```
84 |
85 | --
86 |
87 | Maintained with ❤️ by the [Dart](https://dart.dev) team.
88 |
```
--------------------------------------------------------------------------------
/rockylinux/content.md:
--------------------------------------------------------------------------------
```markdown
1 | # Rocky Linux
2 |
3 | Rocky Linux is a community-supported distribution derived from sources freely provided to the public by [Red Hat](ftp://ftp.redhat.com/pub/redhat/linux/enterprise/) for Red Hat Enterprise Linux (RHEL). As such, Rocky Linux aims to be functionally compatible with RHEL. The Rocky Linux Project mainly changes packages to remove upstream vendor branding and artwork. Rocky Linux is no-cost and free to redistribute. Each Rocky Linux version is maintained for up to 10 years (by means of security updates -- the duration of the support interval by Red Hat has varied over time with respect to Sources released). A new Rocky Linux version is released approximately every 2 years and each Rocky Linux version is periodically updated (roughly every 6 months) to support newer hardware. This results in a secure, low-maintenance, reliable, predictable, and reproducible Linux environment.
4 |
5 | Thank you for using Rocky Linux! We appreciate your feedback and welcome you to the community! Please join us on IRC on Libera.chat in #rockylinux or on our Mattermost instance at https://chat.rockylinux.org
6 |
7 | - [docs.rockylinux.org](https://docs.rockylinux.org)
8 | - [wiki.rockylinux.org](https://wiki.rockylinux.org)
9 |
10 | %%LOGO%%
11 |
12 | # Rocky Linux image documentation
13 |
14 | The `%%IMAGE%%:latest` tag is intentionally missing. Please choose a major version (currently 8 or 9) tag, or a more specific tag to ensure you are pulling the version of Rocky Linux you want: e.g. `%%IMAGE%%:8` or `%%IMAGE%%:9`
15 |
16 | ## Minimal variant
17 |
18 | In addition to the Base container, a Minimal container with microdnf and a stripped down dependency set is available by using any of the `-minimal` tags e.g. `%%IMAGE%%:9-minimal`
19 |
20 | ## Rolling builds
21 |
22 | Rocky Linux offers regularly updated images for all active releases. These images will be updated monthly or as needed for emergency fixes. These rolling updates are tagged with the major version number only. For example: `docker pull %%IMAGE%%:8`.
23 |
24 | ## Minor tags
25 |
26 | Additionally, images with minor version tags that correspond to install media are also offered. **These images DO NOT receive updates** as they are intended to match installation iso contents. If you choose to use these images it is highly recommended that you include `RUN yum -y update && yum clean all` in your Dockerfile, or otherwise address any potential security concerns. To use these images, please specify the minor version tag:
27 |
28 | For example: `docker pull %%IMAGE%%:8.4`
29 |
30 | # Package documentation
31 |
32 | By default, the Rocky Linux containers are built using yum's `nodocs` option, which helps reduce the size of the image. If you install a package and discover files missing, please comment out the line `tsflags=nodocs` in `/etc/yum.conf` and reinstall your package.
33 |
```