vmware/vic-product v1.3.1 on GitHub

Changes from 1.3.0

New Features

vSphere Integrated Containers appliance includes the following new features in this release:

Usability improvements in the Create Virtual Container Host wizard in the vSphere Integrated Containers Plug-In for vSphere Client:
- Separated the Security and Registry Access settings into distinct pages.
- Improved the automatic granting of permissions to the Operations User account.
Modified the procedure to Upgrade the vSphere Integrated Containers Appliance when upgrading from 1.3.0 to 1.3.1. This change is due to the fact that in 1.3.x the vSphere Integrated Containers appliance has four virtual hard disks, whereas in version 1.2.x the appliance has only two disks.
Bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases have been fixed in 1.3.1:

docker run -rm deletes named image volumes #7138
Running docker run -rm should only delete anonymous volumes. However, running docker run -rm against a vSphere Integrated Containers container VM that uses named image volumes results in the deletion of the volume and the loss of all of its data.
Logging into vSphere Integrated Containers Registry from latest versions of Docker client fails. #1346
Attempts to log in to vSphere Integrated Containers Registry from a Docker client that is of a version greater than 17.09.1-ce fail with the error Error response from daemon: [...] certificate is not valid for any names, but wanted to match <cert_common_name>.

See also the resolved issues sections of the release notes for each of the other vSphere Integrated Containers components:

There are no changes to vSphere Integrated Containers Registry or Management Portal in this release. See the full list of all issues fixed in 1.3.1 for all components (requires Zenhub plug-in for Github).

Known Issues

The following issues affect the vSphere Integrated Containers appliance:

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.
Tagging the appliance fails when vCenter password contains colon. #1080
When registering the appliance with the Platform Services Controller, registration fails with the error Failed to locate VIC Appliance. Please check the vCenter Server provided and try again. This problem results from an issue in vSphere 6.5u1, and occurs if the vCenter Single Sign-On password contains a colon (:).
Workaround: Change the vCenter Single Sign-On password. The issue will be fixed in a future vSphere release.
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.
Workaround: Ignore the error message.
Automatically generated certificates for dch-photon are valid for <nil>. #925
vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
Workaround: Download the Management Portal logs manually.

See also the known issues for each of the vSphere Integrated Containers components. There are no changes to vSphere Integrated Containers Registry or Management portal in this release, so the known issues from version 1.3.0 apply for those components.

Download Binaries

Official VMware vSphere Integated Containers 1.3.1 release: http://www.vmware.com/go/download-vic.
Open-source vSphere Integrated Containers project: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.3.1-3409-132fb13d.ova

Installation and Upgrade

For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance.
For instructions about how to upgrade an existing vSphere Integrated Containers appliance, see Upgrade the vSphere Integrated Containers Appliance.

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.

Open Source Components

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

vmware/vic-product v1.3.1 vSphere Integrated Containers Appliance v1.3.1 on GitHub