Skip to content

vSphere Integrated Containers Appliance v1.3.0
Compare
Choose a tag to compare
@mdubya66 mdubya66 released this 04 Jan 23:03
· 657 commits to master since this release
v1.3.0
f8cc731
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Changes from 1.2.1

The VIC Product 1.3.0 OVA Contains

Admiral v1.3.0
Harbor harbor-offline-installer-v1.3.0.tgz
VIC Engine vic_1.3.0.tar.gz
VIC Machine Server digest: sha256:4b49bed2e9a3d3a0c8836d5111cd03e2d196e69ff8f92a9b5cff4040a0fbc40a

New Features

  • Create Virtual Container Host wizard in the vSphere Integrated Containers plug-in for the HTML5 vSphere Client. This feature allows you to deploy VCHs interactively, directly from the vSphere Client. Read more
  • vSphere Integrated Containers Management Portal architecture changed to eventual consistency model. This provides faster updates to the portal and enables a more consistent view between the portal and the status reported by the underlying container hosts.
  • VCHs support 4 virtual NICs, so each VCH network can have a dedicated virtual NIC. Read more
  • Better support for 3rd party registries.
  • Specify a naming convention for container VMs. Read more
  • Support for docker rm -v. Read more
  • Improved scalability and concurrency.

Resolved Issues

The following issues have been resolved since the last release of the vSphere Integrated Containers appliance:

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

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

Known Issues

The following issues affect the vSphere Integrated Containers appliance:

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

    Workaround: If possible, upgrade to vSphere Integrated Containers 1.3.1. If you cannot upgrade, do not use docker run -rm against a container that uses named image volumes.

  • 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>. This issue occurs if the registry is using generated self-signed certificates and you are using the host name to access it.

    Workaround: Use Docker client version 17.09.1-ce or earlier to log in to vSphere Integrated Containers Registry.

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

  • 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

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