Skip to content

vSphere Integrated Containers Appliance v1.4.2
Compare
Choose a tag to compare
@DanielXiao DanielXiao released this 23 Jul 10:55
· 480 commits to master since this release
v1.4.2
4ee4939
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's in the Release Notes

Download

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.2-5659-4ee49390.ova

Filesize (vic-v1.4.2-5659-4ee49390.ova) = 3868856320
SHA256 (vic-v1.4.2-5659-4ee49390.ova) = 6ee254f7c56af0f7118e0f5f41031aa9a3577083c51a880f2d4fe8aa7a11738c
SHA1 (vic-v1.4.2-5659-4ee49390.ova) = 7ac67caa81ea8e36b97ec7ac62644fb65a7461c6
MD5 (vic-v1.4.2-5659-4ee49390.ova) = d5e0a614470ec27d01c5dd3f601884ad

This OVA contains the following component versions:

--admiral v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.2.tgz  \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

Installation and Upgrade

IMPORTANT:

  • vSphere Integrated Containers 1.4.2 includes version 1.4.1 of the vSphere Integrated Containers plug-in for vSphere Client. If you are upgrading vSphere Integrated Containers from version 1.4.1 to 1.4.2, you must still upgrade the client plug-in after you upgrade the appliance. This is so that the plug-in registers correctly with the upgraded appliance. If you do not upgrade the plug-in after upgrading the appliance to 1.4.2, the vSphere Integrated Containers view does not appear in the vSphere Client. For information about upgrading the plug-in, see Upgrade the vSphere Client Plug-Ins on vCenter Server for Windows or Upgrade the vSphere Client Plug-Ins on vCenter Server Appliance.
  • If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. 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 do not work with that version.

Using vSphere Integrated Containers

For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.

Changes

Full list of changes from 1.4.1.

New Features

This release includes the bug fixes listed below.

Enhancements

This release includes the bug fixes listed below.

Resolved Issues

Bumped up Clair to 2.0.4 in vSphere Integrated Containers Registry, fixed issue #5231 (Clair stuck in a loop: "could not branch Ubuntu repository". See vSphere Integrated Containers Registry 1.5.2

Additionally, the following other issues have been addressed:

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.
  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots.

Known Issues

With the exception of the resolved issue above, v1.4.2 has the same known issues as v1.4.1.

View all

  • 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.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • 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:

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.

Assets 2
Loading