Use https:// for links and examples

Found these using `http://[^lp10\*`<][^o]` (to exclude "localhost" and IP-addresses)

Signed-off-by: Sebastiaan van Stijn <[email protected]>

_includes/content/compose-extfields-sub.md

@@ -20,7 +20,7 @@ x-custom:
 ```
 
 The contents of those fields are ignored by Compose, but they can be
-inserted in your resource definitions using [YAML anchors](http://www.yaml.org/spec/1.2/spec.html#id2765878).
+inserted in your resource definitions using [YAML anchors](https://yaml.org/spec/1.2/spec.html#id2765878).
 For example, if you want several of your services to use the same logging
 configuration:
 
@@ -53,7 +53,7 @@ services:
 ```
 
 It is also possible to partially override values in extension fields using
-the [YAML merge type](http://yaml.org/type/merge.html). For example:
+the [YAML merge type](https://yaml.org/type/merge.html). For example:
 
 ```yaml
 version: '3.4'

_includes/content/ssh/ssh-overview.md

@@ -10,5 +10,5 @@ topics below are derived from that GitHub documentation.
 
 Commands for working with SSH keys are described for Mac, Windows, and Linux.
 The Windows steps suggest using [Git Bash](https://git-for-windows.github.io/) but you could also use a tool like
-[PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) or
+[PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) or
 [Bitvise](https://www.bitvise.com/index).

_samples/library/jruby.md

@@ -8,10 +8,10 @@ hide_from_sitemap: true
 redirect_from:
 - /samples/jruby/
 description: |
-  JRuby (http://www.jruby.org) is an implementation of Ruby (http://www.ruby-lang.org) on the JVM.
+  JRuby (https://www.jruby.org) is an implementation of Ruby (https://www.ruby-lang.org/en/) on the JVM.
 ---
 
-JRuby (http://www.jruby.org) is an implementation of Ruby (http://www.ruby-lang.org) on the JVM.
+JRuby (https://www.jruby.org) is an implementation of Ruby (https://www.ruby-lang.org/en/) on the JVM.
 
 
 {% include library-samples.md %}

components.md

@@ -4,12 +4,12 @@ title: Components
 hide_from_sitemap: true
 ---
 
-For components and controls we are using [Bootstrap](http://getbootstrap.com/)
+For components and controls we are using [Bootstrap](https://getbootstrap.com)
 
 
 <!-- ### Dropdowns
 <div class="dropdown">
-  <a id="dLabel" data-target="#" href="http://example.com" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">
+  <a id="dLabel" data-target="#" href="https://example.com" data-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false">
     Dropdown trigger
     <span class="caret"></span>
   </a>
@@ -52,7 +52,7 @@ For components and controls we are using [Bootstrap](http://getbootstrap.com/)
 
 
 ### Accordion
-[Bootstrap docs](http://getbootstrap.com/javascript/#collapse)
+[Bootstrap docs](https://getbootstrap.com/docs/3.4/javascript/)
 <div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
   <div class="panel panel-default">
     <div class="panel-heading" role="tab" id="headingOne">

compose/completion.md

@@ -4,7 +4,7 @@ keywords: fig, composition, compose, docker, orchestration, cli, reference
 title: Command-line completion
 ---
 
-Compose comes with [command completion](http://en.wikipedia.org/wiki/Command-line_completion)
+Compose comes with [command completion](https://en.wikipedia.org/wiki/Command-line_completion)
 for the bash and zsh shell.
 
 ## Install command completion

compose/compose-file/compose-file-v1.md

@@ -22,7 +22,7 @@ how to upgrade, see **[About versions and upgrading](compose-versioning.md)**.
 
 ## Service configuration reference
 
-The Version 1 Compose file is a [YAML](http://yaml.org/) file that defines [services](#service-configuration-reference).
+The Version 1 Compose file is a [YAML](https://yaml.org) file that defines [services](#service-configuration-reference).
 
 The default path for a Compose file is `./docker-compose.yml`.
 

compose/compose-file/compose-file-v2.md

@@ -20,7 +20,7 @@ how to upgrade, see **[About versions and upgrading](compose-versioning.md)**.
 
 ## Service configuration reference
 
-The Compose file is a [YAML](http://yaml.org/) file defining
+The Compose file is a [YAML](https://yaml.org) file defining
 [services](#service-configuration-reference),
 [networks](#network-configuration-reference) and
 [volumes](#volume-configuration-reference).

compose/compose-file/compose-versioning.md

@@ -4,7 +4,7 @@ keywords: fig, composition, compose, versions, upgrading, docker
 title: Compose file versions and upgrading
 ---
 
-The Compose file is a [YAML](http://yaml.org/) file defining services,
+The Compose file is a [YAML](https://yaml.org) file defining services,
 networks, and volumes for a Docker application.
 
 The Compose file formats are now described in these references, specific to each version.

compose/compose-file/index.md

@@ -143,7 +143,7 @@ Compose file.
 
 ## Service configuration reference
 
-The Compose file is a [YAML](http://yaml.org/) file defining
+The Compose file is a [YAML](https://yaml.org) file defining
 [services](#service-configuration-reference),
 [networks](#network-configuration-reference) and
 [volumes](#volume-configuration-reference).

compose/faq.md

@@ -45,7 +45,7 @@ add an explicit signal handler for `SIGTERM`.
         stop_signal: SIGINT
 
 * If you can't modify the application, wrap the application in a lightweight init
-system (like [s6](http://skarnet.org/software/s6/)) or a signal proxy (like
+system (like [s6](https://skarnet.org/software/s6/)) or a signal proxy (like
 [dumb-init](https://github.com/Yelp/dumb-init) or
 [tini](https://github.com/krallin/tini)).  Either of these wrappers takes care of
 handling `SIGTERM` properly.
@@ -79,7 +79,7 @@ containers.
 
 ## Can I use json instead of yaml for my Compose file?
 
-Yes. [Yaml is a superset of json](http://stackoverflow.com/a/1729545/444646) so
+Yes. [Yaml is a superset of json](https://stackoverflow.com/a/1729545/444646) so
 any JSON file should be valid Yaml.  To use a JSON file with Compose,
 specify the filename to use, for example:
 

compose/install.md

@@ -184,7 +184,7 @@ using `pip`, we recommend that you use a
 [virtualenv](https://virtualenv.pypa.io/en/latest/) because many operating
 systems have python system packages that conflict with docker-compose
 dependencies. See the [virtualenv
-tutorial](http://docs.python-guide.org/en/latest/dev/virtualenvs/) to get
+tutorial](https://docs.python-guide.org/dev/virtualenvs/) to get
 started.
 
 ```bash

config/containers/logging/awslogs.md

@@ -11,7 +11,7 @@ The `awslogs` logging driver sends container logs to
 [Amazon CloudWatch Logs](https://aws.amazon.com/cloudwatch/details/#log-monitoring).
 Log entries can be retrieved through the [AWS Management
 Console](https://console.aws.amazon.com/cloudwatch/home#logs:) or the [AWS SDKs
-and Command Line Tools](http://docs.aws.amazon.com/cli/latest/reference/logs/index.html).
+and Command Line Tools](https://docs.aws.amazon.com/cli/latest/reference/logs/index.html).
 
 ## Usage
 
@@ -85,7 +85,7 @@ with the provided endpoint.
 ### awslogs-group
 
 You must specify a
-[log group](http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/WhatIsCloudWatchLogs.html)
+[log group](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html)
 for the `awslogs` logging driver. You can specify the log group with the
 `awslogs-group` log option:
 
@@ -96,7 +96,7 @@ $ docker run --log-driver=awslogs --log-opt awslogs-region=us-east-1 --log-opt a
 ### awslogs-stream
 
 To configure which
-[log stream](http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/WhatIsCloudWatchLogs.html)
+[log stream](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html)
 should be used, you can specify the `awslogs-stream` log option. If not
 specified, the container ID is used as the log stream.
 
@@ -129,7 +129,7 @@ $ docker run \
 ### awslogs-datetime-format
 
 The `awslogs-datetime-format` option defines a multiline start pattern in [Python
-`strftime` format](http://strftime.org). A log message consists of a line that
+`strftime` format](https://strftime.org). A log message consists of a line that
 matches the pattern and any following lines that don't match the pattern. Thus
 the matched line is the delimiter between log messages.
 

config/containers/logging/fluentd.md

@@ -9,9 +9,9 @@ title: Fluentd logging driver
 ---
 
 The `fluentd` logging driver sends container logs to the
-[Fluentd](http://www.fluentd.org/) collector as structured log data. Then, users
+[Fluentd](https://www.fluentd.org) collector as structured log data. Then, users
 can use any of the [various output plugins of
-Fluentd](http://www.fluentd.org/plugins) to write these logs to various
+Fluentd](https://www.fluentd.org/plugins) to write these logs to various
 destinations.
 
 In addition to the log message itself, the `fluentd` log
@@ -133,8 +133,8 @@ Generates event logs in nanosecond resolution. Defaults to `false`.
 
 ## Fluentd daemon management with Docker
 
-About `Fluentd` itself, see [the project webpage](http://www.fluentd.org)
-and [its documents](http://docs.fluentd.org/).
+About `Fluentd` itself, see [the project webpage](https://www.fluentd.org)
+and [its documents](https://docs.fluentd.org).
 
 To use this logging driver, start the `fluentd` daemon on a host. We recommend
 that you use [the Fluentd docker

config/containers/logging/gelf.md

@@ -9,7 +9,7 @@ title: Graylog Extended Format logging driver
 
 The `gelf` logging driver is a convenient format that is understood by a number of tools such as
 [Graylog](https://www.graylog.org/), [Logstash](https://www.elastic.co/products/logstash), and
-[Fluentd](http://www.fluentd.org/). Many tools use this format.
+[Fluentd](https://www.fluentd.org). Many tools use this format.
 
 In GELF, every log message is a dict with the following fields:
 

config/containers/logging/index.md

@@ -20,7 +20,7 @@ may include input from the keyboard or input from another command. `STDOUT` is
 usually a command's normal output, and `STDERR` is typically used to output
 error messages. By default, `docker logs` shows the command's `STDOUT` and
 `STDERR`. To read more about I/O and Linux, see the
-[Linux Documentation Project article on I/O redirection](http://www.tldp.org/LDP/abs/html/io-redirection.html).
+[Linux Documentation Project article on I/O redirection](https://tldp.org/LDP/abs/html/io-redirection.html).
 
 In some cases, `docker logs` may not show useful information unless you take
 additional steps.

config/containers/logging/journald.md

@@ -8,7 +8,7 @@ title: Journald logging driver
 ---
 
 The `journald` logging driver sends container logs to the
-[`systemd` journal](http://www.freedesktop.org/software/systemd/man/systemd-journald.service.html).
+[`systemd` journal](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html).
 Log entries can be retrieved using the `journalctl` command, through use of the
 `journal` API, or using the `docker logs` command.
 

config/containers/logging/splunk.md

@@ -8,7 +8,7 @@ title: Splunk logging driver
 ---
 
 The `splunk` logging driver sends container logs to
-[HTTP Event Collector](http://dev.splunk.com/view/event-collector/SP-CAAAE6M)
+[HTTP Event Collector](https://dev.splunk.com/enterprise/docs/devtools/httpeventcollector/)
 in Splunk Enterprise and Splunk Cloud.
 
 ## Usage

config/containers/runmetrics.md

@@ -177,7 +177,7 @@ Those times are expressed in ticks of 1/100th of a second, also called "user
 jiffies". There are `USER_HZ` *"jiffies"* per second, and on x86 systems,
 `USER_HZ` is 100. Historically, this mapped exactly to the number of scheduler
 "ticks" per second, but higher frequency scheduling and
-[tickless kernels]( http://lwn.net/Articles/549580/) have made the number of
+[tickless kernels](https://lwn.net/Articles/549580/) have made the number of
 ticks irrelevant.
 
 #### Block I/O metrics

config/containers/start-containers-automatically.md

@@ -73,7 +73,7 @@ Keep the following in mind when using restart policies:
 If restart policies don't suit your needs, such as when processes outside
 Docker depend on Docker containers, you can use a process manager such as
 [upstart](http://upstart.ubuntu.com/),
-[systemd](http://freedesktop.org/wiki/Software/systemd/), or
+[systemd](https://freedesktop.org/wiki/Software/systemd/), or
 [supervisor](http://supervisord.org/) instead.
 
 > **Warning**

desktop/enterprise/admin/install/windows.md

@@ -29,7 +29,7 @@ This page contains information about the system requirements and specific instru
 - The following hardware prerequisites are required to successfully run Client
 Hyper-V on Windows 10:
 
-  - 64 bit processor with [Second Level Address Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation)
+  - 64 bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation)
 
   - 4GB system RAM
 

desktop/enterprise/user/mac-user.md

@@ -403,7 +403,7 @@ installed both in Bash and Zsh.
 
 Bash has [built-in support for completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1). To activate completion for Docker commands, these files need to be
 copied or symlinked to your `bash_completion.d/` directory. For example, if you have
-installed bash through [Homebrew](http://brew.sh/).
+installed bash through [Homebrew](https://brew.sh).
 
 ```bash
 etc=/Applications/Docker.app/Contents/Resources/etc
@@ -416,7 +416,7 @@ ln -s $etc/docker-compose.bash-completion $(brew --prefix)/etc/bash_completion.d
 In Zsh, the [completion
 system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html) takes care of things. To activate completion for Docker commands,
 these files need to be copied or symlinked to your Zsh `site-functions/`
-directory. For example, if you installed Zsh through [Homebrew](http://brew.sh/):
+directory. For example, if you installed Zsh through [Homebrew](https://brew.sh):
 
 ```bash
 etc=/Applications/Docker.app/Contents/Resources/etc

desktop/enterprise/user/windows-user.md

@@ -228,7 +228,7 @@ do not need to open port 445 on any other network.
 
 By default, allow connections to `10.0.75.1` on port 445 (the Windows host) from
 `10.0.75.2` (the virtual machine). If your firewall rules seem correct, you may
-need to toggle or [reinstall the File and Print sharing service on the Hyper-V virtual network card](http://stackoverflow.com/questions/42203488/settings-to-windows-firewall-to-allow-docker-for-windows-to-share-drive/43904051#43904051).
+need to toggle or [reinstall the File and Print sharing service on the Hyper-V virtual network card](https://stackoverflow.com/questions/42203488/settings-to-windows-firewall-to-allow-docker-for-windows-to-share-drive/43904051#43904051).
 
 ##### Shared drives on demand
 

develop/develop-images/dockerfile_best-practices.md

@@ -107,7 +107,7 @@ can be useful to perform one-off builds without writing a Dockerfile to disk,
 or in situations where the `Dockerfile` is generated, and should not persist
 afterwards.
 
-> The examples in this section use [here documents](http://tldp.org/LDP/abs/html/here-docs.html)
+> The examples in this section use [here documents](https://tldp.org/LDP/abs/html/here-docs.html)
 > for convenience, but any method to provide the `Dockerfile` on `stdin` can be
 > used.
 > 
@@ -192,7 +192,7 @@ docker build [OPTIONS] -f- PATH
 
 The example below uses the current directory (`.`) as the build context, and builds
 an image using a `Dockerfile` that is passed through `stdin` using a [here
-document](http://tldp.org/LDP/abs/html/here-docs.html).
+document](https://tldp.org/LDP/abs/html/here-docs.html).
 
 ```bash
 # create a directory to work in
@@ -315,7 +315,7 @@ Limiting each container to one process is a good rule of thumb, but it is not a
 hard and fast rule. For example, not only can containers be
 [spawned with an init process](../../engine/reference/run.md#specify-an-init-process),
 some programs might spawn additional processes of their own accord. For
-instance, [Celery](http://www.celeryproject.org/) can spawn multiple worker
+instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker
 processes, and [Apache](https://httpd.apache.org/) can create one process per
 request.
 
@@ -646,7 +646,7 @@ version bumps are easier to maintain, as seen in the following example:
 ```dockerfile
 ENV PG_MAJOR=9.3
 ENV PG_VERSION=9.3.4
-RUN curl -SL http://example.com/postgres-$PG_VERSION.tar.xz | tar -xJC /usr/src/postgress && …
+RUN curl -SL https://example.com/postgres-$PG_VERSION.tar.xz | tar -xJC /usr/src/postgress && …
 ENV PATH=/usr/local/postgres-$PG_MAJOR/bin:$PATH
 ```
 
@@ -729,7 +729,7 @@ have to add another layer in your image. For example, you should avoid doing
 things like:
 
 ```dockerfile
-ADD http://example.com/big.tar.xz /usr/src/things/
+ADD https://example.com/big.tar.xz /usr/src/things/
 RUN tar -xJf /usr/src/things/big.tar.xz -C /usr/src/things
 RUN make -C /usr/src/things all
 ```
@@ -738,7 +738,7 @@ And instead, do something like:
 
 ```dockerfile
 RUN mkdir -p /usr/src/things \
-    && curl -SL http://example.com/big.tar.xz \
+    && curl -SL https://example.com/big.tar.xz \
     | tar -xJC /usr/src/things \
     && make -C /usr/src/things all
 ```
@@ -802,7 +802,7 @@ exec "$@"
 
 > Configure app as PID 1
 >
-> This script uses [the `exec` Bash command](http://wiki.bash-hackers.org/commands/builtin/exec)
+> This script uses [the `exec` Bash command](https://wiki.bash-hackers.org/commands/builtin/exec)
 > so that the final running application becomes the container's PID 1. This
 > allows the application to receive any Unix signals sent to the container.
 > For more, see the [`ENTRYPOINT` reference](../../engine/reference/builder.md#entrypoint).

develop/develop-images/multistage-build.md

@@ -13,7 +13,7 @@ optimize Dockerfiles while keeping them easy to read and maintain.
 > **Acknowledgment**:
 > Special thanks to [Alex Ellis](https://twitter.com/alexellisuk) for granting
 > permission to use his blog post
-> [Builder pattern vs. Multi-stage builds in Docker](http://blog.alexellis.io/mutli-stage-docker-builds/)
+> [Builder pattern vs. Multi-stage builds in Docker](https://blog.alexellis.io/mutli-stage-docker-builds/)
 > as the basis of the examples below.
 
 ## Before multi-stage builds

docker-for-mac/index.md

@@ -284,8 +284,7 @@ certificates](#directory-structures-for-certificates).
 
 For a complete explanation of how to do this, see the blog post [Adding
 Self-signed Registry Certs to Docker & Docker Desktop for
-Mac](http://container-solutions.com/adding-self-signed-registry-certs-docker-mac/){:target="_blank"
-class="_"}.
+Mac](https://blog.container-solutions.com/adding-self-signed-registry-certs-docker-mac){:target="_blank" rel="noopener" class="_"}.
 
 ### Add client certificates
 
@@ -359,7 +358,7 @@ Bash has [built-in support for
 completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1){:target="_blank"
 class="_"} To activate completion for Docker commands, these files need to be
 copied or symlinked to your `bash_completion.d/` directory. For example, if you
-installed bash via [Homebrew](http://brew.sh/):
+installed bash via [Homebrew](https://brew.sh):
 
 ```bash
 etc=/Applications/Docker.app/Contents/Resources/etc
@@ -384,10 +383,10 @@ fi
 ### Zsh
 
 In Zsh, the [completion
-system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html){:target="_blank"
-class="_"} takes care of things. To activate completion for Docker commands,
+system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html){:target="_blank" rel="nooopener" class="_"}
+takes care of things. To activate completion for Docker commands,
 these files need to be copied or symlinked to your Zsh `site-functions/`
-directory. For example, if you installed Zsh via [Homebrew](http://brew.sh/):
+directory. For example, if you installed Zsh via [Homebrew](https://brew.sh){:target="_blank" rel="nooopener" class="_"}:
 
 ```bash
 etc=/Applications/Docker.app/Contents/Resources/etc

docker-for-mac/multi-arch.md

@@ -23,7 +23,7 @@ which means you can run containers for different Linux architectures
 such as `arm`, `mips`, `ppc64le`, and even `s390x`.
 
 This does not require any special configuration in the container itself as it uses
-<a href="http://wiki.qemu.org/" target="_blank" rel="noopener">qemu-static</a> from the **Docker for
+<a href="https://wiki.qemu.org/Main_Page" target="_blank" rel="noopener">qemu-static</a> from the **Docker for
 Mac VM**. Because of this, you can run an ARM container, like the `arm32v7` or `ppc64le`
 variants of the busybox image.