diff --git a/content/engine/swarm/how-swarm-mode-works/nodes.md b/content/engine/swarm/how-swarm-mode-works/nodes.md index 662eef9cc4..113b2eba60 100644 --- a/content/engine/swarm/how-swarm-mode-works/nodes.md +++ b/content/engine/swarm/how-swarm-mode-works/nodes.md @@ -14,7 +14,7 @@ Engine 1.12 or later in swarm mode. There are two types of nodes: [**managers**](#manager-nodes) and [**workers**](#worker-nodes). -![Swarm mode cluster](/engine/swarm/images/swarm-diagram.png) +![Swarm mode cluster](/engine/swarm/images/swarm-diagram.webp) If you haven't already, read through the [swarm mode overview](../index.md) and diff --git a/content/engine/swarm/how-swarm-mode-works/pki.md b/content/engine/swarm/how-swarm-mode-works/pki.md index 927cda4a04..62484e6795 100644 --- a/content/engine/swarm/how-swarm-mode-works/pki.md +++ b/content/engine/swarm/how-swarm-mode-works/pki.md @@ -32,7 +32,7 @@ the lifetime of the node in the current swarm. The diagram below illustrates how manager nodes and worker nodes encrypt communications using a minimum of TLS 1.2. -![TLS diagram](/engine/swarm/images/tls.png) +![TLS diagram](/engine/swarm/images/tls.webp) The example below shows the information from a certificate from a worker node: diff --git a/content/engine/swarm/how-swarm-mode-works/services.md b/content/engine/swarm/how-swarm-mode-works/services.md index f86fff4aa9..a6b691fa13 100644 --- a/content/engine/swarm/how-swarm-mode-works/services.md +++ b/content/engine/swarm/how-swarm-mode-works/services.md @@ -31,7 +31,7 @@ For example, imagine you want to load balance between three instances of an HTTP listener. The diagram below shows an HTTP listener service with three replicas. Each of the three instances of the listener is a task in the swarm. -![ HTTP listener service with three replicas](../images/services-diagram.png) +![ HTTP listener service with three replicas](../images/services-diagram.webp) A container is an isolated process. In the swarm mode model, each task invokes exactly one container. A task is analogous to a “slot” where the scheduler @@ -66,7 +66,7 @@ current version of Docker only supports container tasks. The diagram below shows how swarm mode accepts service create requests and schedules tasks to worker nodes. -![Services flow](../images/service-lifecycle.png) +![Services flow](../images/service-lifecycle.webp) ### Pending services @@ -112,10 +112,10 @@ orchestrator creates a task and the scheduler assigns the task to the new node. Good candidates for global services are monitoring agents, anti-virus scanners or other types of containers that you want to run on every node in the swarm. -The diagram below shows a three-service replica in yellow and a global service -in gray. +The diagram below shows a three-service replica in gray and a global service +in black. -![Global vs replicated services](../images/replicated-vs-global.png) +![Global vs replicated services](../images/replicated-vs-global.webp) ## Learn more diff --git a/content/engine/swarm/images/ingress-lb.png b/content/engine/swarm/images/ingress-lb.png deleted file mode 100644 index 90b750591e..0000000000 Binary files a/content/engine/swarm/images/ingress-lb.png and /dev/null differ diff --git a/content/engine/swarm/images/ingress-lb.webp b/content/engine/swarm/images/ingress-lb.webp new file mode 100644 index 0000000000..621e3cbe8c Binary files /dev/null and b/content/engine/swarm/images/ingress-lb.webp differ diff --git a/content/engine/swarm/images/ingress-routing-mesh.png b/content/engine/swarm/images/ingress-routing-mesh.png deleted file mode 100644 index 55ad8e1fb7..0000000000 Binary files a/content/engine/swarm/images/ingress-routing-mesh.png and /dev/null differ diff --git a/content/engine/swarm/images/ingress-routing-mesh.webp b/content/engine/swarm/images/ingress-routing-mesh.webp new file mode 100644 index 0000000000..7dfa8a4229 Binary files /dev/null and b/content/engine/swarm/images/ingress-routing-mesh.webp differ diff --git a/content/engine/swarm/images/replicated-vs-global.png b/content/engine/swarm/images/replicated-vs-global.png deleted file mode 100644 index bea8acbfa4..0000000000 Binary files a/content/engine/swarm/images/replicated-vs-global.png and /dev/null differ diff --git a/content/engine/swarm/images/replicated-vs-global.webp b/content/engine/swarm/images/replicated-vs-global.webp new file mode 100644 index 0000000000..e812d637c9 Binary files /dev/null and b/content/engine/swarm/images/replicated-vs-global.webp differ diff --git a/content/engine/swarm/images/service-lifecycle.png b/content/engine/swarm/images/service-lifecycle.png deleted file mode 100644 index cd8b86dfce..0000000000 Binary files a/content/engine/swarm/images/service-lifecycle.png and /dev/null differ diff --git a/content/engine/swarm/images/service-lifecycle.webp b/content/engine/swarm/images/service-lifecycle.webp new file mode 100644 index 0000000000..4c89b64e4e Binary files /dev/null and b/content/engine/swarm/images/service-lifecycle.webp differ diff --git a/content/engine/swarm/images/services-diagram.png b/content/engine/swarm/images/services-diagram.png deleted file mode 100644 index e30302ee25..0000000000 Binary files a/content/engine/swarm/images/services-diagram.png and /dev/null differ diff --git a/content/engine/swarm/images/services-diagram.webp b/content/engine/swarm/images/services-diagram.webp new file mode 100644 index 0000000000..41669db454 Binary files /dev/null and b/content/engine/swarm/images/services-diagram.webp differ diff --git a/content/engine/swarm/images/swarm-diagram.png b/content/engine/swarm/images/swarm-diagram.png deleted file mode 100644 index 875330c03b..0000000000 Binary files a/content/engine/swarm/images/swarm-diagram.png and /dev/null differ diff --git a/content/engine/swarm/images/swarm-diagram.webp b/content/engine/swarm/images/swarm-diagram.webp new file mode 100644 index 0000000000..49930c5aff Binary files /dev/null and b/content/engine/swarm/images/swarm-diagram.webp differ diff --git a/content/engine/swarm/images/tls.webp b/content/engine/swarm/images/tls.webp new file mode 100644 index 0000000000..ff200685a8 Binary files /dev/null and b/content/engine/swarm/images/tls.webp differ diff --git a/content/engine/swarm/ingress.md b/content/engine/swarm/ingress.md index 2fb886c25e..d3f42de723 100644 --- a/content/engine/swarm/ingress.md +++ b/content/engine/swarm/ingress.md @@ -73,7 +73,7 @@ the node. For externally routable IP addresses, the port is available from outside the host. For all other IP addresses the access is only available from within the host. -![Service ingress image](images/ingress-routing-mesh.png) +![Service ingress image](images/ingress-routing-mesh.webp) You can publish a port for an existing service using the following command: @@ -202,7 +202,7 @@ You can configure an external load balancer to route requests to a swarm service. For example, you could configure [HAProxy](https://www.haproxy.org) to balance requests to an nginx service published to port 8080. -![Ingress with external load balancer image](images/ingress-lb.png) +![Ingress with external load balancer image](images/ingress-lb.webp) In this case, port 8080 must be open between the load balancer and the nodes in the swarm. The swarm nodes can reside on a private network that is accessible to diff --git a/content/network/drivers/images/ipvlan-l3.png b/content/network/drivers/images/ipvlan-l3.png deleted file mode 100644 index 3227a83ca1..0000000000 Binary files a/content/network/drivers/images/ipvlan-l3.png and /dev/null differ diff --git a/content/network/drivers/images/ipvlan-l3.webp b/content/network/drivers/images/ipvlan-l3.webp new file mode 100644 index 0000000000..888e6c7cb9 Binary files /dev/null and b/content/network/drivers/images/ipvlan-l3.webp differ diff --git a/content/network/drivers/images/macvlan-bridge-ipvlan-l2.png b/content/network/drivers/images/macvlan-bridge-ipvlan-l2.png deleted file mode 100644 index 13aa4f212d..0000000000 Binary files a/content/network/drivers/images/macvlan-bridge-ipvlan-l2.png and /dev/null differ diff --git a/content/network/drivers/images/macvlan-bridge-ipvlan-l2.webp b/content/network/drivers/images/macvlan-bridge-ipvlan-l2.webp new file mode 100644 index 0000000000..d83677b65e Binary files /dev/null and b/content/network/drivers/images/macvlan-bridge-ipvlan-l2.webp differ diff --git a/content/network/drivers/ipvlan.md b/content/network/drivers/ipvlan.md index d44253c60f..91df24c651 100644 --- a/content/network/drivers/ipvlan.md +++ b/content/network/drivers/ipvlan.md @@ -98,7 +98,7 @@ To help understand how this mode interacts with other hosts, the following figure shows the same layer 2 segment between two Docker hosts that applies to and IPvlan L2 mode. -![Multiple IPvlan hosts](images/macvlan-bridge-ipvlan-l2.png) +![Multiple IPvlan hosts](images/macvlan-bridge-ipvlan-l2.webp) The following will create the exact same network as the network `db_net` created earlier, with the driver defaults for `--gateway=192.168.1.1` and `-o ipvlan_mode=l2`. @@ -307,7 +307,7 @@ upstream network will not know about without route distribution. For those curious how IPvlan L3 will fit into container networking, see the following examples. -![Docker IPvlan L2 mode](images/ipvlan-l3.png) +![Docker IPvlan L2 mode](images/ipvlan-l3.webp) IPvlan L3 mode drops all broadcast and multicast traffic. This reason alone makes IPvlan L3 mode a prime candidate for those looking for massive scale and diff --git a/content/storage/_index.md b/content/storage/_index.md index e265f9b4cf..00baa66415 100644 --- a/content/storage/_index.md +++ b/content/storage/_index.md @@ -36,7 +36,7 @@ in the container's filesystem. An easy way to visualize the difference among volumes, bind mounts, and `tmpfs` mounts is to think about where the data lives on the Docker host. -![Types of mounts and where they live on the Docker host](images/types-of-mounts.png) +![Types of mounts and where they live on the Docker host](images/types-of-mounts.webp) - Volumes are stored in a part of the host filesystem which is _managed by Docker_ (`/var/lib/docker/volumes/` on Linux). Non-Docker processes should not diff --git a/content/storage/bind-mounts.md b/content/storage/bind-mounts.md index 36363d8969..9ad952d608 100644 --- a/content/storage/bind-mounts.md +++ b/content/storage/bind-mounts.md @@ -21,7 +21,7 @@ available. If you are developing new Docker applications, consider using [named volumes](volumes.md) instead. You can't use Docker CLI commands to directly manage bind mounts. -![Bind mounts on the Docker host](images/types-of-mounts-bind.png) +![Bind mounts on the Docker host](images/types-of-mounts-bind.webp) ## Choose the -v or --mount flag diff --git a/content/storage/images/types-of-mounts-bind.png b/content/storage/images/types-of-mounts-bind.png deleted file mode 100644 index 2d8d4091b8..0000000000 Binary files a/content/storage/images/types-of-mounts-bind.png and /dev/null differ diff --git a/content/storage/images/types-of-mounts-bind.webp b/content/storage/images/types-of-mounts-bind.webp new file mode 100644 index 0000000000..533efb7cfa Binary files /dev/null and b/content/storage/images/types-of-mounts-bind.webp differ diff --git a/content/storage/images/types-of-mounts-tmpfs.png b/content/storage/images/types-of-mounts-tmpfs.png deleted file mode 100644 index c332c60640..0000000000 Binary files a/content/storage/images/types-of-mounts-tmpfs.png and /dev/null differ diff --git a/content/storage/images/types-of-mounts-tmpfs.webp b/content/storage/images/types-of-mounts-tmpfs.webp new file mode 100644 index 0000000000..35b2f08594 Binary files /dev/null and b/content/storage/images/types-of-mounts-tmpfs.webp differ diff --git a/content/storage/images/types-of-mounts-volume.png b/content/storage/images/types-of-mounts-volume.png deleted file mode 100644 index 229b1ffd17..0000000000 Binary files a/content/storage/images/types-of-mounts-volume.png and /dev/null differ diff --git a/content/storage/images/types-of-mounts-volume.webp b/content/storage/images/types-of-mounts-volume.webp new file mode 100644 index 0000000000..0c8d8d0bd3 Binary files /dev/null and b/content/storage/images/types-of-mounts-volume.webp differ diff --git a/content/storage/images/types-of-mounts.png b/content/storage/images/types-of-mounts.png deleted file mode 100644 index 5950036bba..0000000000 Binary files a/content/storage/images/types-of-mounts.png and /dev/null differ diff --git a/content/storage/images/types-of-mounts.webp b/content/storage/images/types-of-mounts.webp new file mode 100644 index 0000000000..64f380c770 Binary files /dev/null and b/content/storage/images/types-of-mounts.webp differ diff --git a/content/storage/images/volumes-shared-storage.svg b/content/storage/images/volumes-shared-storage.svg deleted file mode 100644 index faaf01640e..0000000000 --- a/content/storage/images/volumes-shared-storage.svg +++ /dev/null @@ -1,121 +0,0 @@ - - - - volumes-shared-storage - Created with Sketch. - - - - - - - - - - - shared file storage - - - - - Datacenter - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - node-3 - - - - - - - Docker - - - - - - service-replica-3 - - - - - - - - - - node-2 - - - - - - - Docker - - - - - - service-replica-2 - - - - - - - - - - node-1 - - - - - - - Docker - - - - - - service-replica-1 - - - - - - - - - - \ No newline at end of file diff --git a/content/storage/images/volumes-shared-storage.webp b/content/storage/images/volumes-shared-storage.webp new file mode 100644 index 0000000000..05e2395105 Binary files /dev/null and b/content/storage/images/volumes-shared-storage.webp differ diff --git a/content/storage/storagedriver/_index.md b/content/storage/storagedriver/_index.md index 547b5ffc5c..538c7a22e4 100644 --- a/content/storage/storagedriver/_index.md +++ b/content/storage/storagedriver/_index.md @@ -73,7 +73,7 @@ writing new files, modifying existing files, and deleting files, are written to this thin writable container layer. The diagram below shows a container based on an `ubuntu:15.04` image. -![Layers of a container based on the Ubuntu image](images/container-layers.jpg) +![Layers of a container based on the Ubuntu image](images/container-layers.webp) A _storage driver_ handles the details about the way these layers interact with each other. Different storage drivers are available, which have advantages @@ -91,7 +91,7 @@ stored in this container layer, multiple containers can share access to the same underlying image and yet have their own data state. The diagram below shows multiple containers sharing the same Ubuntu 15.04 image. -![Containers sharing the same image](images/sharing-layers.jpg) +![Containers sharing the same image](images/sharing-layers.webp) Docker uses storage drivers to manage the contents of the image layers and the writable container layer. Each storage driver handles the implementation diff --git a/content/storage/storagedriver/aufs-driver.md b/content/storage/storagedriver/aufs-driver.md index 2ae447dbb8..fa8d15d0a2 100644 --- a/content/storage/storagedriver/aufs-driver.md +++ b/content/storage/storagedriver/aufs-driver.md @@ -76,7 +76,7 @@ The unification process is referred to as a _union mount_. The diagram below shows a Docker container based on the `ubuntu:latest` image. -![Layers of an Ubuntu container](images/aufs_layers.jpg) +![Layers of an Ubuntu container](images/aufs_layers.webp) Each image layer, and the container layer, are represented on the Docker host as subdirectories within `/var/lib/docker/`. The union mount provides the unified diff --git a/content/storage/storagedriver/btrfs-driver.md b/content/storage/storagedriver/btrfs-driver.md index 2f117264b9..9fc800132b 100644 --- a/content/storage/storagedriver/btrfs-driver.md +++ b/content/storage/storagedriver/btrfs-driver.md @@ -167,14 +167,14 @@ nested and snapshotted. The diagram below shows 4 subvolumes. 'Subvolume 2' and 'Subvolume 3' are nested, whereas 'Subvolume 4' shows its own internal directory tree. -![Subvolume example](images/btfs_subvolume.jpg) +![Subvolume example](images/btfs_subvolume.webp) Only the base layer of an image is stored as a true subvolume. All the other layers are stored as snapshots, which only contain the differences introduced in that layer. You can create snapshots of snapshots as shown in the diagram below. -![Snapshots diagram](images/btfs_snapshots.jpg) +![Snapshots diagram](images/btfs_snapshots.webp) On disk, snapshots look and feel just like subvolumes, but in reality they are much smaller and more space-efficient. Copy-on-write is used to maximize storage @@ -182,7 +182,7 @@ efficiency and minimize layer size, and writes in the container's writable layer are managed at the block level. The following image shows a subvolume and its snapshot sharing data. -![Snapshot and subvolume sharing data](images/btfs_pool.jpg) +![Snapshot and subvolume sharing data](images/btfs_pool.webp) For maximum efficiency, when a container needs more space, it is allocated in *chunks* of roughly 1 GB in size. @@ -192,7 +192,7 @@ own Btrfs subvolume or snapshot. The base layer of an image is stored as a subvolume whereas child image layers and containers are stored as snapshots. This is shown in the diagram below. -![Btrfs container layers](images/btfs_container_layer.jpg) +![Btrfs container layers](images/btfs_container_layer.webp) The high level process for creating images and containers on Docker hosts running the `btrfs` driver is as follows: diff --git a/content/storage/storagedriver/device-mapper-driver.md b/content/storage/storagedriver/device-mapper-driver.md index 16f685e05b..13cb731c65 100644 --- a/content/storage/storagedriver/device-mapper-driver.md +++ b/content/storage/storagedriver/device-mapper-driver.md @@ -740,7 +740,7 @@ container, it is a snapshot of the image the container is based on. The followin example shows a Docker host with two running containers. The first is a `ubuntu` container and the second is a `busybox` container. -![Ubuntu and busybox image layers](images/two_dm_container.jpg) +![Ubuntu and busybox image layers](images/two_dm_container.webp) ## How container reads and writes work with `devicemapper` @@ -750,7 +750,7 @@ With `devicemapper`, reads happen at the block level. The diagram below shows the high level process for reading a single block (`0x44f`) in an example container. -![Reading a block with devicemapper](images/dm_container.jpg) +![Reading a block with devicemapper](images/dm_container.webp) An application makes a read request for block `0x44f` in the container. Because the container is a thin snapshot of an image, it doesn't have the block, but it diff --git a/content/storage/storagedriver/images/aufs_layers.jpg b/content/storage/storagedriver/images/aufs_layers.jpg deleted file mode 100644 index fb0bb39144..0000000000 Binary files a/content/storage/storagedriver/images/aufs_layers.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/aufs_layers.webp b/content/storage/storagedriver/images/aufs_layers.webp new file mode 100644 index 0000000000..903acf64b9 Binary files /dev/null and b/content/storage/storagedriver/images/aufs_layers.webp differ diff --git a/content/storage/storagedriver/images/btfs_container_layer.jpg b/content/storage/storagedriver/images/btfs_container_layer.jpg deleted file mode 100644 index 20fcf1fd3f..0000000000 Binary files a/content/storage/storagedriver/images/btfs_container_layer.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/btfs_container_layer.webp b/content/storage/storagedriver/images/btfs_container_layer.webp new file mode 100644 index 0000000000..7930845247 Binary files /dev/null and b/content/storage/storagedriver/images/btfs_container_layer.webp differ diff --git a/content/storage/storagedriver/images/btfs_pool.jpg b/content/storage/storagedriver/images/btfs_pool.jpg deleted file mode 100644 index 5295b9fb4e..0000000000 Binary files a/content/storage/storagedriver/images/btfs_pool.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/btfs_pool.webp b/content/storage/storagedriver/images/btfs_pool.webp new file mode 100644 index 0000000000..6722175f6c Binary files /dev/null and b/content/storage/storagedriver/images/btfs_pool.webp differ diff --git a/content/storage/storagedriver/images/btfs_snapshots.jpg b/content/storage/storagedriver/images/btfs_snapshots.jpg deleted file mode 100644 index 94c7797aca..0000000000 Binary files a/content/storage/storagedriver/images/btfs_snapshots.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/btfs_snapshots.webp b/content/storage/storagedriver/images/btfs_snapshots.webp new file mode 100644 index 0000000000..d041fcf234 Binary files /dev/null and b/content/storage/storagedriver/images/btfs_snapshots.webp differ diff --git a/content/storage/storagedriver/images/btfs_subvolume.jpg b/content/storage/storagedriver/images/btfs_subvolume.jpg deleted file mode 100644 index 715199d43b..0000000000 Binary files a/content/storage/storagedriver/images/btfs_subvolume.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/btfs_subvolume.webp b/content/storage/storagedriver/images/btfs_subvolume.webp new file mode 100644 index 0000000000..748557aeae Binary files /dev/null and b/content/storage/storagedriver/images/btfs_subvolume.webp differ diff --git a/content/storage/storagedriver/images/container-layers.jpg b/content/storage/storagedriver/images/container-layers.jpg deleted file mode 100644 index 00c30a2043..0000000000 Binary files a/content/storage/storagedriver/images/container-layers.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/container-layers.webp b/content/storage/storagedriver/images/container-layers.webp new file mode 100644 index 0000000000..5ff79bdd81 Binary files /dev/null and b/content/storage/storagedriver/images/container-layers.webp differ diff --git a/content/storage/storagedriver/images/dm_container.jpg b/content/storage/storagedriver/images/dm_container.jpg deleted file mode 100644 index 2a5cd58ccf..0000000000 Binary files a/content/storage/storagedriver/images/dm_container.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/dm_container.webp b/content/storage/storagedriver/images/dm_container.webp new file mode 100644 index 0000000000..1b19e933f5 Binary files /dev/null and b/content/storage/storagedriver/images/dm_container.webp differ diff --git a/content/storage/storagedriver/images/overlay_constructs.jpg b/content/storage/storagedriver/images/overlay_constructs.jpg deleted file mode 100644 index fffe07f560..0000000000 Binary files a/content/storage/storagedriver/images/overlay_constructs.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/overlay_constructs.webp b/content/storage/storagedriver/images/overlay_constructs.webp new file mode 100644 index 0000000000..4b44775463 Binary files /dev/null and b/content/storage/storagedriver/images/overlay_constructs.webp differ diff --git a/content/storage/storagedriver/images/sharing-layers.jpg b/content/storage/storagedriver/images/sharing-layers.jpg deleted file mode 100644 index e59fa833c9..0000000000 Binary files a/content/storage/storagedriver/images/sharing-layers.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/sharing-layers.webp b/content/storage/storagedriver/images/sharing-layers.webp new file mode 100644 index 0000000000..825c56e5d7 Binary files /dev/null and b/content/storage/storagedriver/images/sharing-layers.webp differ diff --git a/content/storage/storagedriver/images/two_dm_container.jpg b/content/storage/storagedriver/images/two_dm_container.jpg deleted file mode 100644 index 18d840d0b0..0000000000 Binary files a/content/storage/storagedriver/images/two_dm_container.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/two_dm_container.webp b/content/storage/storagedriver/images/two_dm_container.webp new file mode 100644 index 0000000000..52b58f4cbc Binary files /dev/null and b/content/storage/storagedriver/images/two_dm_container.webp differ diff --git a/content/storage/storagedriver/images/zfs_clones.jpg b/content/storage/storagedriver/images/zfs_clones.jpg deleted file mode 100644 index 0849aa2454..0000000000 Binary files a/content/storage/storagedriver/images/zfs_clones.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/zfs_clones.webp b/content/storage/storagedriver/images/zfs_clones.webp new file mode 100644 index 0000000000..6258eb8a14 Binary files /dev/null and b/content/storage/storagedriver/images/zfs_clones.webp differ diff --git a/content/storage/storagedriver/images/zfs_zpool.jpg b/content/storage/storagedriver/images/zfs_zpool.jpg deleted file mode 100644 index 17ab2ace50..0000000000 Binary files a/content/storage/storagedriver/images/zfs_zpool.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/zfs_zpool.webp b/content/storage/storagedriver/images/zfs_zpool.webp new file mode 100644 index 0000000000..b3e1c58a3f Binary files /dev/null and b/content/storage/storagedriver/images/zfs_zpool.webp differ diff --git a/content/storage/storagedriver/images/zpool_blocks.jpg b/content/storage/storagedriver/images/zpool_blocks.jpg deleted file mode 100644 index 6fd2482ee6..0000000000 Binary files a/content/storage/storagedriver/images/zpool_blocks.jpg and /dev/null differ diff --git a/content/storage/storagedriver/images/zpool_blocks.webp b/content/storage/storagedriver/images/zpool_blocks.webp new file mode 100644 index 0000000000..8831a66c5d Binary files /dev/null and b/content/storage/storagedriver/images/zpool_blocks.webp differ diff --git a/content/storage/storagedriver/overlayfs-driver.md b/content/storage/storagedriver/overlayfs-driver.md index 665a860264..fd770c3792 100644 --- a/content/storage/storagedriver/overlayfs-driver.md +++ b/content/storage/storagedriver/overlayfs-driver.md @@ -213,7 +213,7 @@ The unified view is exposed through a directory called `merged` which is effectively the containers mount point. The diagram shows how Docker constructs map to OverlayFS constructs. -![How Docker constructs map to OverlayFS constructs](images/overlay_constructs.jpg) +![How Docker constructs map to OverlayFS constructs](images/overlay_constructs.webp) Where the image layer and the container layer contain the same files, the container layer "wins" and obscures the existence of the same files in the image diff --git a/content/storage/storagedriver/zfs-driver.md b/content/storage/storagedriver/zfs-driver.md index d161fe054a..b07b407392 100644 --- a/content/storage/storagedriver/zfs-driver.md +++ b/content/storage/storagedriver/zfs-driver.md @@ -150,7 +150,7 @@ ZFS uses the following objects: The process of creating a clone: -![ZFS snapshots and clones](images/zfs_clones.jpg) +![ZFS snapshots and clones](images/zfs_clones.webp) 1. A read-only snapshot is created from the filesystem. @@ -175,7 +175,7 @@ on a ZFS Snapshot of the top layer of the image it's created from. The diagram below shows how this is put together with a running container based on a two-layer image. -![ZFS pool for Docker container](images/zfs_zpool.jpg) +![ZFS pool for Docker container](images/zfs_zpool.webp) When you start a container, the following steps happen in order: @@ -209,7 +209,7 @@ the dataset it was created from (the snapshots of its parent layers). Read operations are fast, even if the data being read is from a deep layer. This diagram illustrates how block sharing works: -![ZFS block sharing](images/zpool_blocks.jpg) +![ZFS block sharing](images/zpool_blocks.webp) ### Writing files diff --git a/content/storage/tmpfs.md b/content/storage/tmpfs.md index c19e97ae84..5371a21a22 100644 --- a/content/storage/tmpfs.md +++ b/content/storage/tmpfs.md @@ -18,7 +18,7 @@ As opposed to volumes and bind mounts, a `tmpfs` mount is temporary, and only persisted in the host memory. When the container stops, the `tmpfs` mount is removed, and files written there won't be persisted. -![tmpfs on the Docker host](images/types-of-mounts-tmpfs.png) +![tmpfs on the Docker host](images/types-of-mounts-tmpfs.webp) This is useful to temporarily store sensitive files that you don't want to persist in either the host or the container writable layer. diff --git a/content/storage/volumes.md b/content/storage/volumes.md index 568534b7f0..b091ddb914 100644 --- a/content/storage/volumes.md +++ b/content/storage/volumes.md @@ -30,7 +30,7 @@ container's writable layer, because a volume doesn't increase the size of the containers using it, and the volume's contents exist outside the lifecycle of a given container. -![Volumes on the Docker host](images/types-of-mounts-volume.png) +![Volumes on the Docker host](images/types-of-mounts-volume.webp) If your container generates non-persistent state data, consider using a [tmpfs mount](tmpfs.md) to avoid storing the data anywhere permanently, and to @@ -408,7 +408,7 @@ $ docker volume rm nginx-vol When building fault-tolerant applications, you may need to configure multiple replicas of the same service to have access to the same files. -![shared storage](images/volumes-shared-storage.svg) +![shared storage](images/volumes-shared-storage.webp) There are several ways to achieve this when developing your applications. One is to add logic to your application to store files on a cloud object