Skip to content

Commit 3123389

Browse files
bhavin192Misty Stanley-Jones
bhavin192
authored and
Misty Stanley-Jones
committed
Add alt text to images which are missing it (docker#5047)
Signed-off-by: Bhavin Gandhi <[email protected]>
1 parent 86bd21e commit 3123389

24 files changed

+59
-59
lines changed

‎apidocs/overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,4 @@ DTR repositories, permissions, and settings.
1212
To get access to interactive documentation, in your **DTR UI**, click
1313
on the **top-right menu** and choose **API docs**.
1414

15-
![](dtr-api-overview.png)
15+
![API docs page, DTR UI](dtr-api-overview.png)

‎datacenter/install/linux.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Now that UCP is installed, you need to license it. In your browser, navigate
6262
to the UCP web UI, log in with your administrator credentials and upload your
6363
license.
6464

65-
![](../images/try-ddc-1.png){: .with-border}
65+
![UCP login page](../images/try-ddc-1.png){: .with-border}
6666

6767
[Get a free trial license if you don't have one](https://store.docker.com/editions/enterprise/docker-ee-trial).
6868

@@ -71,11 +71,11 @@ license.
7171
Join more nodes so that you can manage them from UCP.
7272
Go to the UCP web UI and navigate to the **Nodes** page.
7373

74-
![](../images/try-ddc-2.png){: .with-border}
74+
![Nodes page](../images/try-ddc-2.png){: .with-border}
7575

7676
Click the **Add Node button** to add a new node.
7777

78-
![](../images/try-ddc-3.png){: .with-border}
78+
![Add node page](../images/try-ddc-3.png){: .with-border}
7979

8080

8181
Check **Add node as a manager** to join the node as a manager

‎docker-cloud/builds/automated-build.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ the code repository service where the image's source code is stored.
6363
Docker's infrastructure, select a builder size to run the build
6464
process on. This hosted build service is free while it is in Beta.
6565

66-
![](images/edit-repository-builds.png)
66+
![Editing build configurations](images/edit-repository-builds.png)
6767

6868
6. If in the previous step you selected **Build on Docker
6969
Cloud’s infrastructure**, then you are given the option to select the

‎docker-cloud/builds/image-scan.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To opt in:
3636

3737
3. Check **Monitor with Docker Security Scanning** to add the service to your plan.
3838

39-
![](images/scan-enable.png)
39+
![Security scanning checkbox](images/scan-enable.png)
4040

4141
The scanning process begins immediately for the three most recent tags in each
4242
of your private repositories. The scan results should be available within 48

‎docker-cloud/builds/link-source.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,10 @@ need to link your source code provider.
2424

2525
3. Click the plug icon for the source provider you want to link.
2626

27-
![](images/source-providers.png)
27+
![Linking source providers](images/source-providers.png)
2828

2929
4. Review the settings for the **Docker Cloud Builder** OAuth application.
30-
![](images/link-source-github-ind.png)
30+
![Granting access to GitHub account](images/link-source-github-ind.png)
3131

3232
>**Note**: If you are the owner of any Github organizations, you might see
3333
options to grant Docker Cloud access to them from this screen. You can also
@@ -56,7 +56,7 @@ from Docker Cloud, *and* from your GitHub account.
5656
4. Go to your GitHub account's **Settings** page.
5757

5858
5. Click **OAuth applications** in the left navigation bar.
59-
![](images/link-source-github-ind-revoke.png)
59+
![Revoking access to GitHub account](images/link-source-github-ind-revoke.png)
6060

6161
6. Click **Revoke** next to the Docker Cloud Builder application.
6262

@@ -78,7 +78,7 @@ case, a **Grant access** button appears next to the organization name in the
7878
link accounts screen, as shown below. If this button does not appear, you must
7979
manually grant the application's access.
8080

81-
![](images/link-source-github-org-lite.png)
81+
![Granting access to GitHub organization](images/link-source-github-org-lite.png)
8282

8383
To manually grant Docker Cloud access to a GitHub organization:
8484

@@ -97,7 +97,7 @@ section at the lower left.
9797
5. Click the pencil icon next to Docker Cloud Builder.
9898

9999
6. Click **Grant access** next to the organization.
100-
![](images/link-source-github-org.png)
100+
![Granting access to GitHub organization manually](images/link-source-github-org.png)
101101

102102
### Revoke access to a GitHub organization
103103

@@ -108,7 +108,7 @@ To revoke Docker Cloud's access to an organization's GitHub repositories:
108108
3. From the Organization Profile menu, click **Third-party access**.
109109
The page displays a list of third party applications and their access status.
110110
4. Click the pencil icon next to Docker Cloud Builder.
111-
![](images/link-source-github-org-revoke.png)
111+
![Revoking access to GitHub organization](images/link-source-github-org-revoke.png)
112112
5. On the next page, click **Deny access**.
113113

114114
## Link to a Bitbucket user account
@@ -121,7 +121,7 @@ To revoke Docker Cloud's access to an organization's GitHub repositories:
121121

122122
4. Click the plug icon for the source provider you want to link.
123123

124-
![](images/source-providers.png)
124+
![Linking Bitbucket](images/source-providers.png)
125125

126126
5. If necessary, log in to Bitbucket.
127127

@@ -151,4 +151,4 @@ unlink it both from Docker Cloud, *and* from your Bitbucket account.
151151
> **Note**: Each repository that is configured as an automated build source
152152
contains a webhook that notifies Docker Cloud of changes in the repository. This
153153
webhook is not automatically removed when you revoke access to a source code
154-
provider.
154+
provider.

‎docker-cloud/builds/repos.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ To store your images in Docker Cloud, you create a repository. All individual us
3030
> **Note**: You do not need to set up automated builds right away, and you can change the build settings at any time after the repository is created. If you choose not to enable automated builds, you can still push images to the repository using the `docker` or `docker-cloud` CLI.
3131
6. Click **Create**.
3232

33-
![](images/create-repository.png)
33+
![Create repository page](images/create-repository.png)
3434

3535
### Repositories for Organizations
3636

@@ -126,7 +126,7 @@ registry.
126126

127127
For example, `registry.com/namespace/reponame` where `registry.com` is the
128128
hostname of the registry.
129-
![](images/third-party-images-modal.png)
129+
![Import repository popup](images/third-party-images-modal.png)
130130

131131
5. Enter credentials for the registry.
132132

‎docker-cloud/cloud-swarm/connect-to-swarm.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ swarm.
2323
2. Click **Swarms** in the top navigation, and click the name of the swarm you want to connect to.
2424
3. Copy the command provided in the dialog that appears.
2525

26-
![](images/swarm-connect.png)
26+
![Connect to swarm popup](images/swarm-connect.png)
2727

2828
4. In a terminal window connected to your local Docker Engine, paste the command, and press **Enter**.
2929

‎docker-cloud/cloud-swarm/link-aws-swarm.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ the new policy to your existing role by following the instructions
8080

8181
The ARN string should look something like `arn:aws:iam::123456789123:role/dockercloud-swarm-role`. You'll use the ARN in the next step.
8282

83-
![](images/aws-swarm-iam-role-2.png)
83+
![Role summary showing Role ARN](images/aws-swarm-iam-role-2.png)
8484

8585
Now skip down to the topic on how to
8686
[Add your AWS account credentials to Docker Cloud](#add-your-aws-account-credentials-to-docker-cloud).
@@ -126,12 +126,12 @@ Role ARN, go back to Docker Cloud to connect the account.
126126
1. In Docker Cloud, click the account menu at the upper right and select **Cloud settings**.
127127
2. In the **Service providers** section, click the plug icon next to Amazon Web Services.
128128

129-
![](images/aws-arn-wizard.png)
129+
![Add AWS Credentials popup](images/aws-arn-wizard.png)
130130

131131
3. Enter the full `Role ARN` for the role you just created.
132132
4. Click **Save**.
133133

134-
![](images/aws-creds-cloud.png)
134+
![Service providers list, showing newly added AWS credentials](images/aws-creds-cloud.png)
135135

136136
You are now ready to deploy a swarm!
137137

‎docker-cloud/cloud-swarm/link-azure-swarm.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You can click a resource from the Dashboard and find the subscription ID under
2424
**Billing -> Subscriptions -> Subscription ID** or simply click
2525
**Subscriptions**, then click a subscription in the list to drill down.
2626

27-
![](images/azure-subscription-id.png)
27+
![Azure subscriptions page](images/azure-subscription-id.png)
2828

2929
When you are ready to add your subscription ID to Docker Cloud,
3030
copy it from your Azure Dashboard.
@@ -39,10 +39,10 @@ select **Cloud settings**.
3939
2. In the **Service Providers** section, click the plug icon next to
4040
Microsoft Azure.
4141

42-
![](images/azure-id-wizard.png)
42+
![Enter Azure subscription ID popup](images/azure-id-wizard.png)
4343

4444
>**Tip:** If you are a member of an Azure Organization, your
45-
admninistrator must first link to Docker Cloud as described in
45+
administrator must first link to Docker Cloud as described in
4646
[Link an Azure Organization as Global Admin](#link-an-azure-organization-as-global-admin).
4747

4848
3. Provide your subscription ID and click **Save**.
@@ -51,7 +51,7 @@ Microsoft Azure.
5151
the two accounts. Your Azure login credentials will automatically populate
5252
to Docker Cloud under **Service Providers -> Microsoft Azure**.
5353

54-
![](images/azure-creds-cloud.png)
54+
![Microsoft Azure entry in Service providers list](images/azure-creds-cloud.png)
5555

5656
## Enable your Azure subscription for Docker Cloud
5757

‎docker-cloud/index.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ also store pre-built images, or link to your source code so it can build the
5757
code into Docker images, and optionally test the resulting images before pushing
5858
them to a repository.
5959

60-
![](images/cloud-build.png)
60+
![Build configuration of repo](images/cloud-build.png)
6161

6262
### Swarm Management (Beta Swarm Mode)
6363

@@ -67,7 +67,7 @@ provision swarms to your cloud providers. Your Docker ID authenticates and
6767
securely accesses personal or team swarms. Docker Cloud allows you to connect
6868
your local Docker Engine to any swarm you have access to in Docker Cloud.
6969

70-
![](images//Beta-Swarm-Mode-List-View.png)
70+
![Swarm mode list](images//Beta-Swarm-Mode-List-View.png)
7171

7272
### Infrastructure management (Standard Mode)
7373

@@ -76,7 +76,7 @@ Docker Cloud allows you to link to your infrastructure or cloud services
7676
provider so you can provision new nodes automatically. Once you have nodes set
7777
up, you can deploy images directly from Docker Cloud repositories.
7878

79-
![](images/cloud-clusters.png)
79+
![Node clusters](images/cloud-clusters.png)
8080

8181
### Services, Stacks, and Applications (Standard Mode)
8282

@@ -86,4 +86,4 @@ containers created from an image), or use Docker Cloud's
8686
[stackfiles](apps/stacks.md) to combine it with other services and
8787
microservices, to form a full application.
8888

89-
![](images/cloud-stack.png)
89+
![Stacks/Wizard - editing yaml file](images/cloud-stack.png)

‎docker-for-azure/deploy.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,13 @@ node can be used for administrating the swarm.
1717
Once you've deployed Docker on Azure, go to the "Outputs" section of the
1818
resource group deployment.
1919

20-
![](img/sshtargets.png)
20+
![SSH targets](img/sshtargets.png)
2121

2222
The "SSH Targets" output is a URL to a blade that describes the IP address
2323
(common across all the manager nodes) and the SSH port (unique for each manager
2424
node) that you can use to log in to each manager node.
2525

26-
![](img/managers.png)
26+
![Swarm managers](img/managers.png)
2727

2828
Obtain the public IP and/or port for the manager node as instructed above and
2929
use the provided SSH key to begin administrating your swarm and the unique port associated with a manager:

‎docker-hub/official_repos.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ To view the Docker Security Scanning results:
7777
You can view Official Images even while logged out, however the scan results are only available once you log in.
7878
2. Navigate to the official repository whose security scan you want to view.
7979
3. Click the `Tags` tab to see a list of tags and their security scan summaries.
80-
![](images/scan-drilldown.gif)
80+
![Viewing CVEs from Docker images](images/scan-drilldown.gif)
8181

8282
You can click into a tag's detail page to see more information about which
8383
layers in the image and which components within the layer are vulnerable.

‎engine/userguide/networking/default_network/ipv6.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ interface.
6969
>
7070
> $ sysctl net.ipv6.conf.eth0.accept_ra=2
7171
72-
![](images/ipv6_basic_host_config.svg)
72+
![IPv6 basic host configuration](images/ipv6_basic_host_config.svg)
7373

7474
Every new container will get an IPv6 address from the defined subnet, and a
7575
default route will be added on `eth0` in the container via the address specified
@@ -104,7 +104,7 @@ Often servers or virtual machines get a `/64` IPv6 subnet assigned (e.g.
104104
Docker a `/80` subnet while using a separate `/80` subnet for other applications
105105
on the host:
106106

107-
![](images/ipv6_slash64_subnet_config.svg)
107+
![IPv6 /64 subnet configuration](images/ipv6_slash64_subnet_config.svg)
108108

109109
In this setup the subnet `2001:db8:23:42::/64` with a range from
110110
`2001:db8:23:42:0:0:0:0` to `2001:db8:23:42:ffff:ffff:ffff:ffff` is attached to
@@ -152,7 +152,7 @@ The Docker subnet is within the subnet managed by your router and connected to
152152
found within the router subnet, and the router can communicate with these
153153
containers directly.
154154

155-
![](images/ipv6_ndp_proxying.svg)
155+
![IPv6 NDP proxying](images/ipv6_ndp_proxying.svg)
156156

157157
When the router wants to send an IPv6 packet to the first container, it
158158
transmits a _neighbor solicitation request_, asking "Who has `2001:db8::c009`?"
@@ -197,7 +197,7 @@ Using routable IPv6 addresses allows you to realize communication between
197197
containers on different hosts. Let's have a look at a simple Docker IPv6 cluster
198198
example:
199199

200-
![](images/ipv6_switched_network_example.svg)
200+
![IPv6 switched network example](images/ipv6_switched_network_example.svg)
201201

202202
The Docker hosts are in the `2001:db8:0::/64` subnet. Host1 is configured to
203203
provide addresses from the `2001:db8:1::/64` subnet to its containers. It has
@@ -246,7 +246,7 @@ routing information about the Docker subnets. When you add or remove a host to
246246
this environment you just have to update the routing table in the router - not
247247
on every host.
248248

249-
![](images/ipv6_routed_network_example.png)
249+
![IPv6 routed network example](images/ipv6_routed_network_example.png)
250250

251251
In this scenario containers of the same host can communicate directly with each
252252
other. The traffic between containers on different hosts will be routed via

‎engine/userguide/networking/work-with-networks.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -332,7 +332,7 @@ needed.
332332
network when you launched it and you connected it to the `isolated_nw` in
333333
step 3.
334334

335-
![](images/working.png)
335+
![Illustration of containers and their networks](images/working.png)
336336

337337
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:03
338338

‎engine/userguide/storagedriver/btrfs-driver.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ own Btrfs subvolume or snapshot. The base layer of an image is stored as a
198198
subvolume whereas child image layers and containers are stored as snapshots.
199199
This is shown in the diagram below.
200200
201-
![](images/btfs_container_layer.jpg)
201+
![Btrfs container layers](images/btfs_container_layer.jpg)
202202
203203
The high level process for creating images and containers on Docker hosts
204204
running the `btrfs` driver is as follows:

‎engine/userguide/storagedriver/imagesandcontainers.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ new files, modifying existing files, and deleting files, are written to this thi
4343
writable container layer. The diagram below shows a container based on the Ubuntu
4444
15.04 image.
4545

46-
![Docker image layers](images/container-layers.jpg)
46+
![Layers of a container based on the Ubuntu image](images/container-layers.jpg)
4747

4848
A _storage driver_ handles the details about the way these layers interact with
4949
each other. Different storage drivers are available, which have advantages
@@ -61,7 +61,7 @@ stored in this container layer, multiple containers can share access to the same
6161
underlying image and yet have their own data state. The diagram below shows
6262
multiple containers sharing the same Ubuntu 15.04 image.
6363

64-
![](images/sharing-layers.jpg)
64+
![Containers sharing same image](images/sharing-layers.jpg)
6565

6666
> **Note**: If you need multiple images to have shared access to the exact
6767
> same data, store this data in a Docker volume and mount it into your
@@ -407,7 +407,7 @@ storage area (`/var/lib/docker/...`). There is also a single shared data volume
407407
located at `/data` on the Docker host. This is mounted directly into both
408408
containers.
409409
410-
![](images/shared-volume.jpg)
410+
![Shared volume across containers](images/shared-volume.jpg)
411411
412412
Data volumes reside outside of the local storage area on the Docker host,
413413
further reinforcing their independence from the storage driver's control. When

‎enterprise/upgrade.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -87,11 +87,11 @@ docker node update --availability active <node>
8787
Once you've upgraded the Docker Engine running on all the nodes, upgrade UCP.
8888
You can do this from the UCP web UI.
8989

90-
![](images/upgrade-1.png){: .with-border}
90+
![UCP update notification banner](images/upgrade-1.png){: .with-border}
9191

9292
Click on the banner, and choose the version you want to upgrade to.
9393

94-
![](images/upgrade-2.png){: .with-border}
94+
![UCP upgrade page - version selection](images/upgrade-2.png){: .with-border}
9595

9696
Once you click **Upgrade UCP**, the upgrade starts. If you want you can upgrade
9797
UCP from the CLI instead. [Learn more](/datacenter/ucp/2.2/guides/admin/install/upgrade.md).
@@ -100,7 +100,7 @@ UCP from the CLI instead. [Learn more](/datacenter/ucp/2.2/guides/admin/install/
100100

101101
Log in into the DTR web UI to check if there's a new version available.
102102

103-
![](images/upgrade-3.png){: .with-border}
103+
![DTR settings page](images/upgrade-3.png){: .with-border}
104104

105105
Then follow these [instructions to upgrade DTR](/datacenter/dtr/2.3/guides/admin/upgrade.md).
106106
When this is finished, your Docker EE has been upgraded.

‎registry/notifications.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ pushes and pulls and layer pushes and pulls. These actions are serialized into
1010
events. The events are queued into a registry-internal broadcast system which
1111
queues and dispatches events to [_Endpoints_](notifications.md#endpoints).
1212

13-
![](images/notifications.png)
13+
![Workflow of registry notifications](images/notifications.png)
1414

1515
## Endpoints
1616

‎swarm/configure-tls.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Swarm Manager, and a Certificate Authority as shown below. All the Docker Engine
1111
hosts (`client`, `swarm`, `node1`, and `node2`) have a copy of the
1212
CA's certificate as well as their own key-pair signed by the CA.
1313

14-
![](images/tls-1.jpg)
14+
![Swarm cluster, Docker client, CA server, Swarm Manager](images/tls-1.jpg)
1515

1616
You will complete the following steps in this procedure:
1717

@@ -307,7 +307,7 @@ follows on each node:
307307
308308
When the copying is complete, each machine should have the following keys.
309309
310-
![](images/tls-2.jpeg)
310+
![List of keys on each machine](images/tls-2.jpeg)
311311
312312
Each node in your infrastructure should have the following files in the
313313
`/home/ubuntu/.certs/` directory:

0 commit comments

Comments
 (0)