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

Remove edge-only admonitions

This commit is contained in:
Misty Stanley-Jones 2017-06-26 10:49:11 -07:00 committed by Misty Stanley-Jones
parent 3b5192d199
commit 7f966c4c10
6 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
engine/admin/logging/awslogs.md
View File

@ -77,8 +77,6 @@ specified, the container ID is used as the log stream.
### awslogs-create-group ### awslogs-create-group
{% include edge_only.md section="option" %}
Log driver will return an error by default if the log group does not exist. However, you can set the Log driver will return an error by default if the log group does not exist. However, you can set the
`awslogs-create-group` to `true` to automatically create the log group as needed. `awslogs-create-group` to `true` to automatically create the log group as needed.
The `awslogs-create-group` option defaults to `false`. The `awslogs-create-group` option defaults to `false`.

1
engine/admin/logging/overview.md
View File

@ -19,7 +19,6 @@ In addition to using the logging drivers included with Docker, you can also
implement and use [logging driver plugins](/engine/admin/logging/plugins.md). implement and use [logging driver plugins](/engine/admin/logging/plugins.md).
Logging driver plugins are available in Docker 17.05 and higher. Logging driver plugins are available in Docker 17.05 and higher.
{% include edge_only.md section="feature" %}
## Configure the default logging driver ## Configure the default logging driver

2
engine/admin/logging/plugins.md
View File

@ -4,8 +4,6 @@ title: Use a logging driver plugin
keywords: logging, driver, plugins, monitoring keywords: logging, driver, plugins, monitoring
--- ---
{% include edge_only.md section="page" %}
Docker logging plugins allow you to extend and customize Docker's logging Docker logging plugins allow you to extend and customize Docker's logging
capabilities beyond those of the [built-in logging drivers](overview.md). capabilities beyond those of the [built-in logging drivers](overview.md).
A logging service provider can A logging service provider can

2
engine/swarm/networking.md
View File

@ -259,8 +259,6 @@ DNS round robin (DNSRR). You can configure this per service.
## Customize the ingress network ## Customize the ingress network
{% include edge_only.md section="feature" %}
Most users never need to configure the `ingress` network, but Docker 17.05 and Most users never need to configure the `ingress` network, but Docker 17.05 and
higher allow you to do so. This can be useful if the automatically-chosen subnet higher allow you to do so. This can be useful if the automatically-chosen subnet
conflicts with one that already exists on your network, or you need to customize conflicts with one that already exists on your network, or you need to customize

3
engine/swarm/services.md
View File

@ -472,7 +472,6 @@ flag. For more information, see
### Control service scale and placement ### Control service scale and placement
{% include edge_only.md section="options" %}
Swarm mode has two types of services: replicated and global. For replicated Swarm mode has two types of services: replicated and global. For replicated
services, you specify the number of replica tasks for the swarm manager to services, you specify the number of replica tasks for the swarm manager to
schedule onto available nodes. For global services, the scheduler places one schedule onto available nodes. For global services, the scheduler places one
@ -540,8 +539,6 @@ labels to ensure that your service is deployed to the appropriate swarm nodes.
### Specify service placement preferences (--placement-pref) ### Specify service placement preferences (--placement-pref)
{% include edge_only.md section="feature" %}
You can set up the service to divide tasks evenly over different categories of You can set up the service to divide tasks evenly over different categories of
nodes. One example of where this can be useful is to balance tasks over a set nodes. One example of where this can be useful is to balance tasks over a set
of datacenters or availability zones. The example below illustrates this: of datacenters or availability zones. The example below illustrates this:

3
engine/userguide/eng-image/multistage-build.md
View File

@ -4,8 +4,6 @@ keywords: images, containers, best practices
title: Use multi-stage builds title: Use multi-stage builds
--- ---
{% include edge_only.md section="page" %}
Multi-stage builds are a new feature in Docker 17.05, and they will be exciting Multi-stage builds are a new feature in Docker 17.05, and they will be exciting
to anyone who has struggled to optimize Dockerfiles while keeping them easy to to anyone who has struggled to optimize Dockerfiles while keeping them easy to
read and maintain. read and maintain.
@ -156,4 +154,3 @@ CMD ["./app"]
- Check out the blog post - Check out the 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](http://blog.alexellis.io/mutli-stage-docker-builds/)
for full source code and a walk-through of these examples. for full source code and a walk-through of these examples.
- Check out other features available in [Docker Edge](/edge/)