From 4d281c4b64a4a3b01e85931990b82775301a9170 Mon Sep 17 00:00:00 2001 From: Docker Library Bot Date: Fri, 13 Sep 2019 23:17:44 +0000 Subject: [PATCH] Run update.sh --- adoptopenjdk/README.md | 2 +- golang/README.md | 2 +- haxe/README.md | 2 +- hylang/README.md | 2 +- julia/README.md | 2 +- mongo/README.md | 2 +- nextcloud/README.md | 6 +++--- node/README.md | 4 ++-- openjdk/README.md | 2 +- perl/README.md | 4 ++-- php/README.md | 2 +- pypy/README.md | 4 ++-- python/README.md | 4 ++-- redis/README.md | 2 +- ruby/README.md | 4 ++-- rust/README.md | 4 ++-- swift/README.md | 2 +- traefik/README.md | 28 +++++++++++++++++++++++----- 18 files changed, 48 insertions(+), 30 deletions(-) diff --git a/adoptopenjdk/README.md b/adoptopenjdk/README.md index 11c2dc4ee..a403c4998 100644 --- a/adoptopenjdk/README.md +++ b/adoptopenjdk/README.md @@ -284,7 +284,7 @@ The `adoptopenjdk` images come in many flavors, each designed for a specific use This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like bionic in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. +Some of these tags may have names like bionic in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu. ## `adoptopenjdk:-windowsservercore` diff --git a/golang/README.md b/golang/README.md index f4ea96978..1a3cd7bc2 100644 --- a/golang/README.md +++ b/golang/README.md @@ -163,7 +163,7 @@ The `golang` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `golang:-alpine` diff --git a/haxe/README.md b/haxe/README.md index 53b340a44..ebd1b18db 100644 --- a/haxe/README.md +++ b/haxe/README.md @@ -204,7 +204,7 @@ The `haxe` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `haxe:-windowsservercore` diff --git a/hylang/README.md b/hylang/README.md index 033f5c0c6..1d9fb3b72 100644 --- a/hylang/README.md +++ b/hylang/README.md @@ -132,7 +132,7 @@ The `hylang` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `hylang:-alpine` diff --git a/julia/README.md b/julia/README.md index 038ace63e..478c370f5 100644 --- a/julia/README.md +++ b/julia/README.md @@ -101,7 +101,7 @@ The `julia` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `julia:-windowsservercore` diff --git a/mongo/README.md b/mongo/README.md index 0a6a58b81..62055c0d4 100644 --- a/mongo/README.md +++ b/mongo/README.md @@ -306,7 +306,7 @@ The `mongo` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like bionic or xenial in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. +Some of these tags may have names like bionic or xenial in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu. ## `mongo:-windowsservercore` diff --git a/nextcloud/README.md b/nextcloud/README.md index 96ac8e9e2..8a86370f6 100644 --- a/nextcloud/README.md +++ b/nextcloud/README.md @@ -25,9 +25,9 @@ WARNING: - [`16.0.4-apache`, `16.0-apache`, `16-apache`, `apache`, `stable-apache`, `production-apache`, `16.0.4`, `16.0`, `16`, `latest`, `stable`, `production`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/16.0/apache/Dockerfile) - [`16.0.4-fpm-alpine`, `16.0-fpm-alpine`, `16-fpm-alpine`, `fpm-alpine`, `stable-fpm-alpine`, `production-fpm-alpine`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/16.0/fpm-alpine/Dockerfile) - [`16.0.4-fpm`, `16.0-fpm`, `16-fpm`, `fpm`, `stable-fpm`, `production-fpm`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/16.0/fpm/Dockerfile) -- [`17.0.0beta4-apache`, `17.0.0-beta-apache`, `17.0-beta-apache`, `17-beta-apache`, `17.0.0beta4`, `17.0.0-beta`, `17.0-beta`, `17-beta`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/17.0-beta/apache/Dockerfile) -- [`17.0.0beta4-fpm-alpine`, `17.0.0-beta-fpm-alpine`, `17.0-beta-fpm-alpine`, `17-beta-fpm-alpine`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/17.0-beta/fpm-alpine/Dockerfile) -- [`17.0.0beta4-fpm`, `17.0.0-beta-fpm`, `17.0-beta-fpm`, `17-beta-fpm`](https://github.com/nextcloud/docker/blob/73ff5c860d155d46ed65b6ae9caa9ee6e64478de/17.0-beta/fpm/Dockerfile) +- [`17.0.0RC1-apache`, `17.0.0-rc-apache`, `17.0-rc-apache`, `17-rc-apache`, `17.0.0RC1`, `17.0.0-rc`, `17.0-rc`, `17-rc`](https://github.com/nextcloud/docker/blob/ba4fc2dcbb50617656d5a167fb4c2a5d5bed8e19/17.0-rc/apache/Dockerfile) +- [`17.0.0RC1-fpm-alpine`, `17.0.0-rc-fpm-alpine`, `17.0-rc-fpm-alpine`, `17-rc-fpm-alpine`](https://github.com/nextcloud/docker/blob/ba4fc2dcbb50617656d5a167fb4c2a5d5bed8e19/17.0-rc/fpm-alpine/Dockerfile) +- [`17.0.0RC1-fpm`, `17.0.0-rc-fpm`, `17.0-rc-fpm`, `17-rc-fpm`](https://github.com/nextcloud/docker/blob/ba4fc2dcbb50617656d5a167fb4c2a5d5bed8e19/17.0-rc/fpm/Dockerfile) # Quick reference diff --git a/node/README.md b/node/README.md index ef07d14c0..2e13ba41b 100644 --- a/node/README.md +++ b/node/README.md @@ -88,9 +88,9 @@ The `node` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like buster, jessie, or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `node:-slim` diff --git a/openjdk/README.md b/openjdk/README.md index 3fc1ca80e..9247c27f4 100644 --- a/openjdk/README.md +++ b/openjdk/README.md @@ -216,7 +216,7 @@ The `openjdk` images come in many flavors, each designed for a specific use case This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `openjdk:` (from 12 onwards), `openjdk:-oracle` and `openjdk:-oraclelinux7` diff --git a/perl/README.md b/perl/README.md index accf6ab56..5f95fe65b 100644 --- a/perl/README.md +++ b/perl/README.md @@ -158,9 +158,9 @@ The `perl` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `perl:-slim` diff --git a/php/README.md b/php/README.md index 5778f4532..a2c8b6a65 100644 --- a/php/README.md +++ b/php/README.md @@ -265,7 +265,7 @@ COPY config/opcache.ini $PHP_INI_DIR/conf.d/ The `php` images come in many flavors, each designed for a specific use case. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `php:-cli` diff --git a/pypy/README.md b/pypy/README.md index 3cad51ac4..09da5cc17 100644 --- a/pypy/README.md +++ b/pypy/README.md @@ -119,9 +119,9 @@ The `pypy` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like jessie or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like jessie or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `pypy:-slim` diff --git a/python/README.md b/python/README.md index 560f107c8..def5c3911 100644 --- a/python/README.md +++ b/python/README.md @@ -183,9 +183,9 @@ The `python` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `python:-slim` diff --git a/redis/README.md b/redis/README.md index 4fc0fcc2a..4c5171cb2 100644 --- a/redis/README.md +++ b/redis/README.md @@ -126,7 +126,7 @@ The `redis` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like buster in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +Some of these tags may have names like buster in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. ## `redis:-alpine` diff --git a/ruby/README.md b/ruby/README.md index 916967787..30bd85ec4 100644 --- a/ruby/README.md +++ b/ruby/README.md @@ -136,9 +136,9 @@ The `ruby` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `ruby:-slim` diff --git a/rust/README.md b/rust/README.md index 88a30583a..077973c4c 100644 --- a/rust/README.md +++ b/rust/README.md @@ -97,9 +97,9 @@ The `rust` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. +Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian. -Some of these tags may have names like buster or stretch in them. These are the suite code names for releases of [Debian](https://wiki.debian.org/DebianReleases) and indicate which release the image is based on. +This tag is based off of [`buildpack-deps`](https://hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of Docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. ## `rust:-slim` diff --git a/swift/README.md b/swift/README.md index 7a52de93b..1c4655935 100644 --- a/swift/README.md +++ b/swift/README.md @@ -107,7 +107,7 @@ The `swift` images come in many flavors, each designed for a specific use case. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. -Some of these tags may have names like bionic or xenial in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. +Some of these tags may have names like bionic or xenial in them. These are the suite code names for releases of [Ubuntu](https://wiki.ubuntu.com/Releases) and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Ubuntu. ## `swift:-slim` diff --git a/traefik/README.md b/traefik/README.md index e3781db1f..e0ba623b0 100644 --- a/traefik/README.md +++ b/traefik/README.md @@ -16,10 +16,11 @@ WARNING: # Supported tags and respective `Dockerfile` links -- [`v2.0.0-rc3`, `2.0.0-rc3`, `v2.0`, `2.0`, `montdor`](https://github.com/containous/traefik-library-image/blob/65a0466cd3336a0fd048ef4b06cd9a08a9edae6e/scratch/Dockerfile) -- [`v2.0.0-rc3-alpine`, `2.0.0-rc3-alpine`, `v2.0-alpine`, `2.0-alpine`, `montdor-alpine`](https://github.com/containous/traefik-library-image/blob/65a0466cd3336a0fd048ef4b06cd9a08a9edae6e/alpine/Dockerfile) -- [`v1.7.15`, `1.7.15`, `v1.7`, `1.7`, `maroilles`, `latest`](https://github.com/containous/traefik-library-image/blob/7fdb3306ad96133928541d5305b771173aab0313/scratch/Dockerfile) -- [`v1.7.15-alpine`, `1.7.15-alpine`, `v1.7-alpine`, `1.7-alpine`, `maroilles-alpine`, `alpine`](https://github.com/containous/traefik-library-image/blob/7fdb3306ad96133928541d5305b771173aab0313/alpine/Dockerfile) +- [`v2.0.0-rc4`, `2.0.0-rc4`, `v2.0`, `2.0`, `montdor`](https://github.com/containous/traefik-library-image/blob/9895566e03b5800b431d5ee89a7b56b39f612b59/alpine/Dockerfile) +- [`v2.0.0-rc4-windowsservercore-1809`, `2.0.0-rc4-windowsservercore-1809`, `v2.0-windowsservercore-1809`, `2.0-windowsservercore-1809`, `montdor-windowsservercore-1809`](https://github.com/containous/traefik-library-image/blob/9895566e03b5800b431d5ee89a7b56b39f612b59/windows/1809/Dockerfile) +- [`v1.7.16`, `1.7.16`, `v1.7`, `1.7`, `maroilles`, `latest`](https://github.com/containous/traefik-library-image/blob/c35c242498450bb31333770ec3bce26260020d6f/scratch/Dockerfile) +- [`v1.7.16-alpine`, `1.7.16-alpine`, `v1.7-alpine`, `1.7-alpine`, `maroilles-alpine`, `alpine`](https://github.com/containous/traefik-library-image/blob/c35c242498450bb31333770ec3bce26260020d6f/alpine/Dockerfile) +- [`v1.7.16-windowsservercore-1809`, `1.7.16-windowsservercore-1809`, `v1.7-windowsservercore-1809`, `1.7-windowsservercore-1809`, `maroilles-windowsservercore-1809`, `windowsservercore-1809`](https://github.com/containous/traefik-library-image/blob/c35c242498450bb31333770ec3bce26260020d6f/windows/1809/Dockerfile) # Quick reference @@ -33,7 +34,7 @@ WARNING: [the Traefik Project](https://github.com/containous/traefik-library-image) - **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64)) - [`amd64`](https://hub.docker.com/r/amd64/traefik/), [`arm32v6`](https://hub.docker.com/r/arm32v6/traefik/), [`arm64v8`](https://hub.docker.com/r/arm64v8/traefik/) + [`amd64`](https://hub.docker.com/r/amd64/traefik/), [`arm32v6`](https://hub.docker.com/r/arm32v6/traefik/), [`arm64v8`](https://hub.docker.com/r/arm64v8/traefik/), [`windows-amd64`](https://hub.docker.com/r/winamd64/traefik/) - **Published image artifact details**: [repo-info repo's `repos/traefik/` directory](https://github.com/docker-library/repo-info/blob/master/repos/traefik) ([history](https://github.com/docker-library/repo-info/commits/master/repos/traefik)) @@ -177,6 +178,23 @@ A community support is available at [https://community.containo.us](https://comm A collection of contributions around Traefik can be found at [https://awesome.traefik.io](https://awesome.traefik.io). +# Image Variants + +The `traefik` images come in many flavors, each designed for a specific use case. + +## `traefik:` + +This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. + +## `traefik:-windowsservercore` + +This image is based on [Windows Server Core (`microsoft/windowsservercore`)](https://hub.docker.com/r/microsoft/windowsservercore/). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016. + +For information about how to get Docker running on Windows, please see the relevant "Quick Start" guide provided by Microsoft: + +- [Windows Server Quick Start](https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_server) +- [Windows 10 Quick Start](https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start_windows_10) + # License View [license information](https://github.com/containous/traefik/blob/master/LICENSE.md) for the software contained in this image.