github vmware/vic-product v1.2.1
VIC Product v1.2.1

latest releases: v1.5.8, v1.5.8-rc1, v1.5.8-dev...
6 years ago
SHA-256 e903d10eec08317b72f649a47403347b4091fb2c4632f1bee4f5915adbc039e9  vic-v1.2.1-4104e5f9.ova
SHA-1 bb4209f7c660450ed9fd6fe788ce9c33d57571fe  vic-v1.2.1-4104e5f9.ova
MD5 9bd2ac2a591915e6f8e73ee3ad683e5c  vic-v1.2.1-4104e5f9.ova
4697.92 MB

Changes from 1.2.0 releases/1.2.0...releases/1.2.1

New Features

This release fixes issues related to using vSphere Integrated Containers in an environment that uses an external Platform Services Controller.

Resolved Issues

  • Deployment of appliance fails if vSphere administrator user is not in the @vsphere.local domain. #771
    If your vSphere domain is not @vsphere.local, deployment of the appliance succeeds, but registration with the Platform Services Controller fails and vSphere Integrated Containers services do not start.
  • Harbor registry fails to start when CA signed certificate added during OVA deployment #797
  • Upgrading the VIC appliance fails with external PSC BugRef 1962217 #837

See also the resolved issues for each of the vSphere Integrated Containers components:

Known Issues

The following issues affect the vSphere Integrated Containers appliance:

  • Attempts to log in to vSphere Integrated Containers Registry from Docker fail with error 401 Unauthorized #891
    When you attempt to log in to vSphere Integrated Containers Registry, you see a 401 Unauthorized error, even though you have correctly configured the Docker client with the registry certificate and you have successfully logged in to that registry instance before. This issue can occur if the vSphere Integrated Containers appliance has experienced a hard reset.

    Workaround: In the vSphere Client, restart the vSphere Integrated Containers appliance by selecting Power > Restart Guest OS.

  • vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
    Workaround: Download the Management Portal logs manually.

  • dch-photon image is not present in default-project after upgrade. #769
    If you perform a fresh installation of vSphere Integrated Containers 1.2, the dch-photon image is present in default-project. If you upgrade vSphere Integrated Containers 1.1.x to 1.2, dch-photon image is not present.

    Workaround: Pull the vmware/dch-photon image from Docker Hub.

See also the known issues for each of the vSphere Integrated Containers components:

Download Binaries

Official VMware vSphere Integated Containers 1.2.1 release: http://www.vmware.com/go/download-vic.

Installation

For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy 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/index.html#getting-started.

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.

Don't miss a new vic-product release

NewReleases is sending notifications on new releases.