vSphere Integrated Containers enables VMware customers to deliver a production-ready container solution to their developers and DevOps teams.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.8-7942-4cc5e276.ova
File size: 2977228800
SHA256 checksum: 815f861845c3a5696e29363092a856b74bc5c6e65df78cc0a20138e9e8208796
SHA1 checksum: 63f04a54496ab78fb6bdd064ee4c0436048c89e7
MD5 checksum: 4cf190cd052a6c0b650d682b6ae21b83
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.8 resolves an issue in which when vCenter Server is inaccessible, for example due to upgrade or backup and restore operations, and container creation or deletion operations are in progress, vSphere Integrated Containers cannot find those containers, and reports No such container errors in the log.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.8:
Full list of changes from 1.5.7.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.8 has the same known issues as v1.5.7.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.7-7923-f6c04457.ova
File size: 2850846720
SHA256 checksum: 27820fb3bf3a306ee048f8b06c038fe7bedb3c1d2a6547dc51371d557ba37959
SHA1 checksum: fcfc57033cc6b2dafd54cdbc0aa98418e927c625
MD5 checksum: cead7cdea51c40d3b13954f50fef3dc0
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.7 includes the following new features:
vSphere Integrated Containers 1.5.7 includes the bug fixes listed in Resolved Issues below.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.7:
Full list of changes from 1.5.6.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.7 has the same known issues as v1.5.6.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.6-7849-bd6fe58a.ova
File size: 2769541120
SHA256 checksum: 745cf6c4dbfeda99fb860d52d55b5324f07fb4b5e399c92fec29d14b3ea3d48
SHA1 checksum: 1b433059fef3098c1f1ff7bef96d625e1ad6a71c
MD5 checksum: 9a0d88ce14ab5395586f025650fbd5bd
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.6 includes the following new features:
vSphere Integrated Containers 1.5.6 includes the bug fixes listed in Resolved Issues below.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.6:
Full list of changes from 1.5.5.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.6 has the same known issues as v1.5.5.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.5-7767-a7161963.ova
File size: 2665861120
SHA256 checksum: 657d534999bd16d29d376461c8edb71d1cb753972eebfe8fdfa25c07acfdf723
SHA1 checksum: 264f30293de90c6a3c7f1c3c1bd183fd2bdd8ace
MD5 checksum: 0365afc522c1653e42d0bd4f395dd7b7
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.5 includes support for vCenter Server version 7.0.
vSphere Integrated Containers 1.5.5 includes the bug fixes listed in Resolved Issues below.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.5:
Full list of changes from 1.5.4.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.5 has the same known issues as v1.5.4.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.4-7589-e70af4fe.ova
File size: 2613698560
SHA256 checksum: 6d136b3506e34da0fb03c2eec381f24b2ef405c0d7e33b4d10cbb7222d61a923
SHA1 checksum: 016c729ebefd9a37af63e8621c8bf03b05b65507
MD5 checksum: c77443cf5f45eee017fcc329542581e7
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.4 includes support for vCenter Server version 6.7 update 3.
vSphere Integrated Containers 1.5.4 includes the bug fixes listed in Resolved Issues below.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.4:
Full list of changes from 1.5.3.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.4 has the same known issues as v1.5.3.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.3-7511-ba6b1644.ova
File size: 2478755840
SHA256 checksum: f7559a655d460a11751dffdb299157e62cc2955c1fbbb977e595d340b58bced7
SHA1 checksum: d938bf19ff3c8843da2fededc923074a38e42a11
MD5 checksum: f426f65903d47a552ac36f110fd7533e
This OVA contains the following component versions:
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
vSphere Integrated Containers 1.5.3 includes the following new features:
ca.pem file in the vic-machine configure command. Read more.--registry-ca option of the the vic-machine configure command replaces certificates instead of just adding them. Read more.vSphere Integrated Containers Engine 1.5.3 includes the bug fixes listed in Resolved Issues below.
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.3:
Full list of changes from 1.5.2.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.3 has the same known issues as v1.5.2.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.2-7206-92ebfaf5.ova
File size: 2468853760
SHA256 checksum: d200d6d928d22041aac447f1070a7a6f712beb7cf84c4300b9a428ab003cf3ea
SHA1 checksum: 85a1ae2a3a8a19cf1c75f2f44960cbef1028560b
MD5 checksum: 09d355c36b4f7699e8a497c559689e65
This OVA contains the following component versions:
Appliance: https://github.com/vmware/vic-product/archive/v1.5.2.zip
Engine: https://github.com/vmware/vic/archive/v1.5.2.zip
Harbor: https://github.com/goharbor/harbor/archive/v1.7.4.zip
Admiral: https://github.com/vmware/admiral/archive/vic_v1.5.2.zip
Plug-In: https://github.com/vmware/vic-ui/archive/v1.5.2.zip
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
Full list of changes from 1.5.1.
vSphere Integrated Containers 1.5.2 includes the following new features:
vSphere Integrated Containers 1.5.2 includes the following enhancements:
Fixes an issue that caused upgrading from 1.5.0 to 1.5.1 to fail.
Updates the version of runc in the vSphere Integrated Containers OVA appliance, to address a critical vulnerability that allows specially-crafted containers to gain administrative privileges on the host. The version of runc in the dch-photon image on Docker Hub has also been updated. For more information, see CVE-2019-5736.
IMPORTANT: vSphere Integrated Containers virtual container host (VCH) endpoint VMs are not vulnerable to the privilege escalation described in CVE-2019-5736. This issue affected the OVA appliance because it uses a standard container engine to run the vSphere Integrated Containers services. The dch-photon image includes a standard Docker Engine. Container VMs that you deploy by using vSphere Integrated Containers VCHs are not vulnerable to the runc vulnerability.
See also the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.2 has the same known issues as v1.5.1.
Appliance upgrade script does not support FQDN addresses for the old appliance #1731
When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.1-6995-a6158aac.ova
File size: 2526382080
SHA256 checksum: 3e50c461351e47762b977158852196bdb864b6d932e66ef9576d9e70b58d08b0
SHA1 checksum: 80c0249985bef23ae8a1a4760c3345f19afbd0d2
MD5 checksum: 44c8f6970d63b253ba687828ab085ff5
This OVA contains the following component versions:
Appliance: https://github.com/vmware/vic-product/archive/v1.5.1.zip
Engine: https://github.com/vmware/vic/archive/v1.5.0.zip
Registry: https://github.com/goharbor/harbor/archive/v1.7.1.zip
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.5.0.zip
UI: https://github.com/vmware/vic-ui/archive/v1.5.0.zip
IMPORTANT: Upgrading from 1.5.0 to 1.5.1 fails. VMware is working on a solution. Upgrading from versions prior to 1.5.0 to 1.5.1 works as normal.
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
Full list of changes from 1.5.0.
vSphere Integrated Containers 1.5.1 includes no new features.
vSphere Integrated Containers 1.5.1 includes no new enhancements.
vSphere Integrated Containers 1.5.1 updates the version of runc in the vSphere Integrated Containers OVA appliance, to address a critical vulnerability that allows specially-crafted containers to gain administrative privileges on the host. The version of runc in the dch-photon image on Docker Hub has also been updated. For more information, see CVE-2019-5736.
IMPORTANT: vSphere Integrated Containers virtual container host (VCH) endpoint VMs are not vulnerable to the privilege escalation described in CVE-2019-5736. This issue affected the OVA appliance because it uses a standard container engine to run the vSphere Integrated Containers services. The dch-photon image includes a standard Docker Engine. Container VMs that you deploy by using vSphere Integrated Containers VCHs are not vulnerable to the runc vulnerability.
Upgrading from 1.5.0 to 1.5.1 fails. VMware is working on a solution. Upgrading from versions prior to 1.5.0 to 1.5.1 works as normal.
Apart from the upgrade issue above, vSphere Integrated Containers appliance 1.5.1 has the same known issues as v1.5.0.
Appliance upgrade script does not support FQDN addresses for the old appliance #1731
When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.0-6915-e18e6647.ova
File size: 2524979200
SHA256 checksum: 183c68214b7c9fdbfaf619cd6a368fd3a2500a9d518ce2b9fd2e14e991445b82
SHA1 checksum: 6f0c6931807da2bc915836f6ae1ff7e0a407599a
MD5 checksum: 13cecb6068bef241fafff6d04d55462c
This OVA contains the following component versions:
Appliance: https://github.com/vmware/vic-product/archive/v1.5.0.zip
Engine: https://github.com/vmware/vic/archive/v1.5.0.zip
Registry: https://github.com/goharbor/harbor/archive/v1.7.1.zip
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.5.0.zip
UI: https://github.com/vmware/vic-ui/archive/v1.5.0.zip
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
Full list of changes from 1.4.4.
vSphere Integrated Containers 1.5.0 includes the following new features:
--storage-quota option to vic-machine create and configure, to set a limit on the amount of storage that a VCH can consume. Read more.vSphere Integrated Containers 1.5.0 includes the following enhancements:
COMPOSE_TLS_VERSION in the env file that is generated during VCH deployment. Read more.No issues that were documented as known issues in previous releases have been fixed in vSphere Integrated Containers appliance 1.5.0. See the resolved issues for each of the vSphere Integrated Containers components:
vSphere Integrated Containers appliance 1.5.0 has the same known issues as v1.4.4.
Appliance upgrade script does not support FQDN addresses for the old appliance #1731
When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.
Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic
Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.4-6375-0a6da3d4.ova
File size: 3342868480
SHA256 checksum: 06131aebed1d2fe4299fb9cefcb18d0bc1f2fba4a700660ce94c43f6735f0d93
SHA1 checksum: 1b9dc717225cb0f02bcc2358176cabac8bdc9222
MD5 checksum: 652ebc88cef35cbe1e22207ef41f9287
This OVA contains the following component versions:
Appliance: https://github.com/vmware/vic-product/archive/v1.4.4.zip
Engine: https://github.com/vmware/vic/archive/v1.4.3.zip
Registry: https://github.com/goharbor/harbor/archive/v1.5.4.zip
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.4.3.zip
UI: https://github.com/vmware/vic-ui/archive/v1.4.4.zip
IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or 1.4.4. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client might not work with that version. Only versions 1.4.3 and 1.4.4 have been verified with vSphere 6.7 update 1.
For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.
Full list of changes from 1.4.3.
vSphere Integrated Containers 1.4.4 includes no new features.
vSphere Integrated Containers 1.4.4 includes the bug fixes listed in Resolved Issues below.
There are no resolved issues in the vSphere Integrated Containers appliance in this release. This release includes fixes for issues that are resolved in new versions of vSphere Integrated Containers Registry and the vSphere Integrated Containers UI:
vic-machine command in the Create VCH wizard and a UI deployment issue. See the Resolved Issues for vSphere Integrated Containers UI 1.4.4.With the exception of the resolved issue above, v1.4.4 has the same known issues as v1.4.3.
Appliance upgrade script does not support FQDN addresses for the old appliance #1731
When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172
The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.
Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.
Workaround: Ignore the warnings and click Yes to proceed with the operation.
See also the known issues for each of the vSphere Integrated Containers components:
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.