Skip to content

VIC Product v1.2.0
Compare
Choose a tag to compare
@andrewtchin andrewtchin released this 09 Sep 04:31
· 862 commits to master since this release
v1.2.0
d0ea01c 
SHA-256 4d1b77ab292142665aef9347e14a7e1de5b6c23fe9174172ea3740140f605d6d  vic-v1.2.0-d0ea01c2.ova
SHA-1 e5c465a6383d538ac6153711237690e06f1daad6  vic-v1.2.0-d0ea01c2.ova
MD5 22ee79121415099d729bfbf4a9496281  vic-v1.2.0-d0ea01c2.ova
4645.14 MB

New Features

  • Authentication and authorization, implementing vCenter Single Sign On across components and role-based access control at the project level. Read more
  • Full integration of the vSphere Integrated Containers Registry and Management Portal user interfaces. Read more
  • Container security with trusted content and scanning for security vulnerabilities, with policies set per project. Read more
  • Reconfigure deployed virtual container hosts (VCHs). Read more
  • Improved functionality for the vSphere administrator in the vSphere Client. Read more
  • A fully functional Docker Engine in vSphere Integrated Containers, that allows developers and cloud admins to deploy docker container hosts. Read more
  • Support for the Docker commit, diff, stats, and cp commands. Read more

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

    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.

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

    Workaround: Create or use an administrator account in the @vsphere.local domain to deploy the appliance and register it with the Platform Services Controller.

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

Download Binaries

Official VMware vSphere Integated Containers 1.2.0 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.

Assets 2
Loading