Skip to content

Releases: vmware/vic-product

vSphere Integrated Containers Appliance v1.4.0-rc4

04 May 18:41
@andrewtchin andrewtchin
v1.4.0-rc4
d99cbdb
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.0-rc4 Pre-release
Pre-release

Download OVA

Filesize: 3.1 GB
SHA256: 6707aa37cf4a239aade8295c700b4ec464ae5175ed7515f49f9c7cca6a86ec89
SHA1: b5c248fe82d8559a7496ebdd1bd3bd0cbc18a638
MD5: 15fbc45aef2a5d49a681db84247fdcf2

OVA will contain:

appliance=v1.4.0-rc4-4839-d99cbdb4
harbor=harbor-offline-installer-v1.5.0-rc5.tgz
engine=vic_v1.4.0-rc2.tar.gz
admiral=vmware/admiral:vic_v1.4.0-rc4 45a773ffae33
vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:latest b3412e003674

Changes from v1.3.1

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.0-rc3

01 May 21:27
@andrewtchin andrewtchin
v1.4.0-rc3
d99cbdb
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.0-rc3 Pre-release
Pre-release

Download OVA

Filesize: 3.26G
SHA256: 9dd22418e3ea05cff84e39de17abf50020129323525cff173c0530aafff68878
SHA1: 94fe3e1e5be5d03b4c961bce7da04f9aea227323
MD5: 1a7e40d2ef81918acd83b8fa7487b5c0

OVA will contain:

appliance=v1.4.0-rc3-4824-d99cbdb4
harbor=harbor-offline-installer-v1.5.0-rc4.tgz
engine=vic_v1.4.0-rc2.tar.gz
admiral=vmware/admiral:vic_v1.4.0-rc4 45a773ffae33
vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:latest b3412e003674

Changes from v1.3.1

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.0-rc2

26 Apr 20:07
@andrewtchin andrewtchin
v1.4.0-rc2
f02b325
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.0-rc2 Pre-release
Pre-release

OVA will contain:

appliance=v1.4.0-rc2-4741-f02b3258
harbor=harbor-offline-installer-v1.5.0-rc3.tgz
engine=vic_v1.4.0-rc2.tar.gz
admiral=vmware/admiral:vic_v1.4.0-rc3 515cd800e655
vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:latest b3412e003674
Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.0-rc1

17 Apr 15:28
@andrewtchin andrewtchin
v1.4.0-rc1
9894cca
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.0-rc1 Pre-release
Pre-release

OVA will contain:

appliance=v1.4.0-rc1-4516-9894ccaa
harbor=harbor-offline-installer-v1.5.0-rc1.tgz
engine=vic_v1.4.0-rc1.tar.gz
admiral=vmware/admiral:vic_v1.4.0-rc1 25b429a30c3d
vic-machine-server=gcr.io/eminent-nation-87317/vic-machine-server:dev a79c45066d57

New Features

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

  • Support for vSphere 6.7
  • Support for vSphere Remote Office Branch Office (ROBO) Advanced
  • Improved upgrade procedure

Resolved Issues

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

  • 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 (:).
  • vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
    Workaround: Download the Management Portal logs manually.

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

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.

  • 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

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

Download Binaries

Open-source vSphere Integrated Containers project: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.0-rc1-4516-9894ccaa.ova

Installation and Upgrade

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.

NOTE: This documentation is a work-in-progress and has not yet been fully updated for 1.4.0.

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

vSphere Integrated Containers Engine Version 1.5.0 Dev

17 Apr 14:01
@mhagen-vmware mhagen-vmware
v1.5.0-dev
9894cca
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Engine Version 1.5.0 Dev Pre-release
Pre-release

This release tagged with the dev tag for the master branch and future release version. It will also serve as the location for our pre-release software bundles.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.3.1

05 Feb 19:27
@mdubya66 mdubya66
v1.3.1
132fb13
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.3.1

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:

  • 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

Installation and Upgrade

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.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.3.1-rc3

03 Feb 18:26
@mdubya66 mdubya66
v1.3.1-rc3
132fb13
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.3.1-rc3 Pre-release
Pre-release

No changes from rc2. Rev'd to pick up vic-ui rc2.

Assets 2
Loading

vSphere Integrated Containers Appliance v1.3.1-rc2

03 Feb 18:26
@andrewtchin andrewtchin
v1.3.1-rc2
132fb13
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.3.1-rc2 Pre-release
Pre-release

Changes from 1.3.0

Assets 2
Loading

vSphere Integrated Containers Appliance v1.3.1-rc1

29 Jan 01:33
@mdubya66 mdubya66
v1.3.1-rc1
b1b156e
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.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.3.1-rc1 Pre-release
Pre-release

Changes from 1.3.0

Assets 2
Loading

vSphere Integrated Containers Appliance v1.3.0

04 Jan 23:03
@mdubya66 mdubya66
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
Learn about vigilant mode.
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.3.0

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