Documented issue with excessive image layers (#1980)

vmware · Aug 30, 2018 · 275aefa · 275aefa
1 parent 0587c06
commit 275aefa
Show file tree

Hide file tree

Showing 5 changed files with 24 additions and 1 deletion.
diff --git a/docs/user_doc/SUMMARY.md b/docs/user_doc/SUMMARY.md
@@ -132,6 +132,7 @@
          * [Default Volume Store Error](vic_vsphere_admin/ts_volume_store_error.md)
          * [Deleting or Inspecting a VCH Fails](vic_vsphere_admin/ts_delete_inspect_error.md)
          * [Docker Login Fails](vic_vsphere_admin/ts_dockerlogin_error.md)
+         * [Image Store Error](vic_vsphere_admin/ts_imagestore_error.md)
      * [Install Packages in VCHs](vic_vsphere_admin/vch_install_packages.md)
          * [Mount an NFS Share Point](vic_vsphere_admin/vch_mount_nfsshare.md)
   * [Security Reference](vic_vsphere_admin/security_reference.md)

diff --git a/docs/user_doc/vic_app_dev/container_limitations.md b/docs/user_doc/vic_app_dev/container_limitations.md
@@ -36,6 +36,7 @@ vSphere Integrated Containers Engine includes these limitations:
 	- IPv6
 	- Service discovery
 - Containers can acquire DHCP addresses only if they are on a network that has DHCP.
+- When you use a standard Docker Engine, an image can have a maximum of 120 layers. When you use a vSphere Integrated Containers Engine virtual container host (VCH), an image can have a maximum of 90 layers. For more information, see [Pulling Images into VCHs Fails with Image Store Error](../vic_vsphere_admin/ts_imagestore_error.md) in the Troubleshooting section.
 
 ## Using `docker-compose` with TLS
 

diff --git a/docs/user_doc/vic_vsphere_admin/SUMMARY.md b/docs/user_doc/vic_vsphere_admin/SUMMARY.md
@@ -115,6 +115,7 @@
          * [Default Volume Store Error](ts_volume_store_error.md)
          * [Deleting or Inspecting a VCH Fails](ts_delete_inspect_error.md)
          * [Docker Login Fails](ts_dockerlogin_error.md)
+         * [Image Store Error](ts_imagestore_error.md)
      * [Install Packages in VCHs](vch_install_packages.md)
          * [Mount an NFS Share Point](vch_mount_nfsshare.md)
   * [Security Reference](security_reference.md)

diff --git a/docs/user_doc/vic_vsphere_admin/ts_imagestore_error.md b/docs/user_doc/vic_vsphere_admin/ts_imagestore_error.md
@@ -0,0 +1,19 @@
+# Pulling Images into VCHs Fails with Image Store Error #
+
+When you attempt to pull certain container images from a registry into a vSphere Integrated Containers virtual container host (VCH), the pulls fail with an error. Pulls of other container images do not fail.
+
+## Problem
+
+When you attempt to pull an image, you see the following error:
+
+<pre>Failed to write to image store: [POST /storage/{<i>image_store_name</i>}] [5000] WriteImage default &{Code: 500 Message:Failed to add disk 'scsi0:0' .}
+</pre>
+
+
+## Cause
+
+When you use a standard Docker Engine, an image can have a maximum of 120 layers. When you use a vSphere Integrated Containers Engine virtual container host (VCH), an image can have a maximum of 90 layers. The image that you are pulling exceeds the limit of 90 layers.
+
+## Solution
+
+Reduce the number of layers in the image to less than 90.
diff --git a/docs/user_doc/vic_vsphere_admin/ts_post_deployment_op.md b/docs/user_doc/vic_vsphere_admin/ts_post_deployment_op.md
@@ -6,4 +6,5 @@ This section provides solutions for common problems that you might encounter whe
 * [Some Users Cannot Access vSphere Integrated Containers Services](ts_no_access_to_vic_services.md)
 * [Default Volume Store Error](ts_volume_store_error.md)
 * [Deleting or Inspecting a VCH Fails with a Not a VCH or Resource Pool Not Found Error](ts_delete_inspect_error.md)
-* [Logging in to vSphere Integrated Containers Registry from Docker Fails](ts_dockerlogin_error.md)
+* [Logging in to vSphere Integrated Containers Registry from Docker Fails](ts_dockerlogin_error.md)
+* [Pulling Images into VCHs Fails with Image Store Error](ts_imagestore_error.md)