Skip to content

Releases: vmware/vic-product

vSphere Integrated Containers Appliance v1.5.8

02 Sep 12:45
@stuclem stuclem
v1.5.8
4cc5e27
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.5.8 Latest
Latest

Title

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.8-7942-4cc5e276.ova

File size: 2977228800
SHA256 checksum: 815f861845c3a5696e29363092a856b74bc5c6e65df78cc0a20138e9e8208796
SHA1 checksum: 63f04a54496ab78fb6bdd064ee4c0436048c89e7
MD5 checksum: 4cf190cd052a6c0b650d682b6ae21b83

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.8 resolves an issue in which when vCenter Server is inaccessible, for example due to upgrade or backup and restore operations, and container creation or deletion operations are in progress, vSphere Integrated Containers cannot find those containers, and reports No such container errors in the log.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.8:

Full list of changes from 1.5.7.

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

Known Issues

vSphere Integrated Containers appliance 1.5.8 has the same known issues as v1.5.7.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.7

06 Apr 10:51
@stuclem stuclem
v1.5.7
f6c0445
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.5.7

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.7-7923-f6c04457.ova

File size: 2850846720
SHA256 checksum: 27820fb3bf3a306ee048f8b06c038fe7bedb3c1d2a6547dc51371d557ba37959
SHA1 checksum: fcfc57033cc6b2dafd54cdbc0aa98418e927c625
MD5 checksum: cead7cdea51c40d3b13954f50fef3dc0

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.7 includes the following new features:

  • Support for vSphere 7u2. To use the vSphere Integrated Containers UI plugin with vSphere 7u2, you must use vSphere Integrated Containers v1.5.7. Version 1.5.6 is not compatible with vSphere 7u2.
  • Support for Harbor 1.7.8, which resolves an issue with an expired sudo version. See goharbor/harbor#11633 for details.
  • Bug fixes and Security updates.

Enhancements

vSphere Integrated Containers 1.5.7 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.7:

Full list of changes from 1.5.6.

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

Known Issues

vSphere Integrated Containers appliance 1.5.7 has the same known issues as v1.5.6.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.6

28 Oct 13:51
@stuclem stuclem
v1.5.6
bd6fe58
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.5.6

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.6-7849-bd6fe58a.ova

File size: 2769541120
SHA256 checksum: 745cf6c4dbfeda99fb860d52d55b5324f07fb4b5e399c92fec29d14b3ea3d48
SHA1 checksum: 1b433059fef3098c1f1ff7bef96d625e1ad6a71c
MD5 checksum: 9a0d88ce14ab5395586f025650fbd5bd

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.6 includes the following new features:

  • Support for vCenter Server version 7.0u1.
  • TLS 1.1 is disabled. TLS 1.2 has already been supported for several releases. Read more.

Enhancements

vSphere Integrated Containers 1.5.6 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.6:

  • VMware CA is missing in VIC appliance OVA. 2304

Full list of changes from 1.5.5.

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

Known Issues

vSphere Integrated Containers appliance 1.5.6 has the same known issues as v1.5.5.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.5

13 Apr 08:46
@VinodJIsaac VinodJIsaac
v1.5.5
a716196
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.5.5

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.5-7767-a7161963.ova

File size: 2665861120
SHA256 checksum: 657d534999bd16d29d376461c8edb71d1cb753972eebfe8fdfa25c07acfdf723
SHA1 checksum: 264f30293de90c6a3c7f1c3c1bd183fd2bdd8ace
MD5 checksum: 0365afc522c1653e42d0bd4f395dd7b7

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.5 includes support for vCenter Server version 7.0.

Enhancements

vSphere Integrated Containers 1.5.5 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.5:

  • VMware CA is missing in VIC appliance OVA. 2304

Full list of changes from 1.5.4.

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

Known Issues

vSphere Integrated Containers appliance 1.5.5 has the same known issues as v1.5.4.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.4

23 Sep 10:24
@stuclem stuclem
v1.5.4
e70af4f
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.5.4

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.4-7589-e70af4fe.ova

File size: 2613698560
SHA256 checksum: 6d136b3506e34da0fb03c2eec381f24b2ef405c0d7e33b4d10cbb7222d61a923
SHA1 checksum: 016c729ebefd9a37af63e8621c8bf03b05b65507
MD5 checksum: c77443cf5f45eee017fcc329542581e7

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.4 includes support for vCenter Server version 6.7 update 3.

Enhancements

vSphere Integrated Containers 1.5.4 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.4:

  • VMware CA is missing in VIC appliance OVA. 2304

Full list of changes from 1.5.3.

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

Known Issues

vSphere Integrated Containers appliance 1.5.4 has the same known issues as v1.5.3.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.3

01 Jul 09:06
@stuclem stuclem
v1.5.3
ba6b164
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.5.3

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.3-7511-ba6b1644.ova

File size: 2478755840
SHA256 checksum: f7559a655d460a11751dffdb299157e62cc2955c1fbbb977e595d340b58bced7
SHA1 checksum: d938bf19ff3c8843da2fededc923074a38e42a11
MD5 checksum: f426f65903d47a552ac36f110fd7533e

This OVA contains the following component versions:

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.

Changes

New Features

vSphere Integrated Containers 1.5.3 includes the following new features:

  • Support for vCenter Server versions 6.7 up to and including 6.7 update 2. Read more.
  • Support for NSX-T Data Center version 2.4. Read more.
  • New option to reconfigure the appliance settings to change the TLS certificates after you have deployed it. Read more.
  • Support for FQDN of the old version of the appliance in the upgrade script. Read more.
  • Option to configure the path to an existing ca.pem file in the vic-machine configure command. Read more.
  • Option to forward appliance logs to Syslog servers. Read more.
  • Option to roll back the VCH configuration changes to the previous settings. Read more.
  • The --registry-ca option of the the vic-machine configure command replaces certificates instead of just adding them. Read more.
  • Increases the length of the root password to 128 characters. Read more. 
  • Option to click on the vSphere Integrated Containers appliance IP address in the vSphere Integrated Containers Summary tab to go to the vSphere Integrated Containers Getting Started page. Read more. 

Enhancements

vSphere Integrated Containers Engine 1.5.3 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.3:

  • Cannot browse default-vic-registry when Proxy is set. PR 2478
  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses.

Full list of changes from 1.5.2.

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

Known Issues

vSphere Integrated Containers appliance 1.5.3 has the same known issues as v1.5.2.

View all

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.2

15 Mar 13:12
@stuclem stuclem
v1.5.2
92ebfaf
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.5.2

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.2-7206-92ebfaf5.ova

File size: 2468853760
SHA256 checksum: d200d6d928d22041aac447f1070a7a6f712beb7cf84c4300b9a428ab003cf3ea
SHA1 checksum: 85a1ae2a3a8a19cf1c75f2f44960cbef1028560b
MD5 checksum: 09d355c36b4f7699e8a497c559689e65

This OVA contains the following component versions:

Appliance: https://github.com/vmware/vic-product/archive/v1.5.2.zip
Engine: https://github.com/vmware/vic/archive/v1.5.2.zip
Harbor: https://github.com/goharbor/harbor/archive/v1.7.4.zip
Admiral: https://github.com/vmware/admiral/archive/vic_v1.5.2.zip
Plug-In: https://github.com/vmware/vic-ui/archive/v1.5.2.zip

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.

Changes

Full list of changes from 1.5.1.

New Features

vSphere Integrated Containers 1.5.2 includes the following new features:

  • New option to set subnet masks on user-defined bridge networks. Read more
  • New option to limit the number of container VMs that a VCH can host. Read more

Enhancements

vSphere Integrated Containers 1.5.2 includes the following enhancements:

  • Setting the client network gateway is optional in the Create VCH wizard. Read more

Resolved Issues

  • Fixes an issue that caused upgrading from 1.5.0 to 1.5.1 to fail.

  • Updates the version of runc in the vSphere Integrated Containers OVA appliance, to address a critical vulnerability that allows specially-crafted containers to gain administrative privileges on the host. The version of runc in the dch-photon image on Docker Hub has also been updated. For more information, see CVE-2019-5736.

    IMPORTANT: vSphere Integrated Containers virtual container host (VCH) endpoint VMs are not vulnerable to the privilege escalation described in CVE-2019-5736. This issue affected the OVA appliance because it uses a standard container engine to run the vSphere Integrated Containers services. The dch-photon image includes a standard Docker Engine. Container VMs that you deploy by using vSphere Integrated Containers VCHs are not vulnerable to the runc vulnerability.

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

Known Issues

vSphere Integrated Containers appliance 1.5.2 has the same known issues as v1.5.1.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.1

18 Feb 10:15
@stuclem stuclem
v1.5.1
a6158aa
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.5.1

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.1-6995-a6158aac.ova

File size: 2526382080
SHA256 checksum: 3e50c461351e47762b977158852196bdb864b6d932e66ef9576d9e70b58d08b0
SHA1 checksum: 80c0249985bef23ae8a1a4760c3345f19afbd0d2
MD5 checksum: 44c8f6970d63b253ba687828ab085ff5

This OVA contains the following component versions:

Appliance: https://github.com/vmware/vic-product/archive/v1.5.1.zip
Engine: https://github.com/vmware/vic/archive/v1.5.0.zip 
Registry: https://github.com/goharbor/harbor/archive/v1.7.1.zip 
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.5.0.zip 
UI: https://github.com/vmware/vic-ui/archive/v1.5.0.zip

Installation and Upgrade

IMPORTANT: Upgrading from 1.5.0 to 1.5.1 fails. VMware is working on a solution. Upgrading from versions prior to 1.5.0 to 1.5.1 works as normal.

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.

Changes

Full list of changes from 1.5.0.

New Features

vSphere Integrated Containers 1.5.1 includes no new features.

Enhancements

vSphere Integrated Containers 1.5.1 includes no new enhancements.

Resolved Issues

vSphere Integrated Containers 1.5.1 updates the version of runc in the vSphere Integrated Containers OVA appliance, to address a critical vulnerability that allows specially-crafted containers to gain administrative privileges on the host. The version of runc in the dch-photon image on Docker Hub has also been updated. For more information, see CVE-2019-5736.

IMPORTANT: vSphere Integrated Containers virtual container host (VCH) endpoint VMs are not vulnerable to the privilege escalation described in CVE-2019-5736. This issue affected the OVA appliance because it uses a standard container engine to run the vSphere Integrated Containers services. The dch-photon image includes a standard Docker Engine. Container VMs that you deploy by using vSphere Integrated Containers VCHs are not vulnerable to the runc vulnerability.

Known Issues

Upgrading from 1.5.0 to 1.5.1 fails. VMware is working on a solution. Upgrading from versions prior to 1.5.0 to 1.5.1 works as normal.

Apart from the upgrade issue above, vSphere Integrated Containers appliance 1.5.1 has the same known issues as v1.5.0.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.5.0

15 Jan 15:42
@stuclem stuclem
v1.5.0
e18e664
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.5.0

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.5.0-6915-e18e6647.ova

File size: 2524979200
SHA256 checksum: 183c68214b7c9fdbfaf619cd6a368fd3a2500a9d518ce2b9fd2e14e991445b82
SHA1 checksum: 6f0c6931807da2bc915836f6ae1ff7e0a407599a
MD5 checksum: 13cecb6068bef241fafff6d04d55462c

This OVA contains the following component versions:

Appliance: https://github.com/vmware/vic-product/archive/v1.5.0.zip 
Engine: https://github.com/vmware/vic/archive/v1.5.0.zip 
Registry: https://github.com/goharbor/harbor/archive/v1.7.1.zip 
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.5.0.zip 
UI: https://github.com/vmware/vic-ui/archive/v1.5.0.zip

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.

Changes

Full list of changes from 1.4.4.

New Features

vSphere Integrated Containers 1.5.0 includes the following new features:

  • Support for the use of NSX-T Data Center logical switches for all VCH networks. Read more.
  • Support for the use of an alternative Linux kernel ISO from which to boot container VMs. Read more.
  • Upgraded the OS of all vSphere Integrated Containers components to Photon OS 2.0. Read more.
  • Addition of the --storage-quota option to vic-machine create and configure, to set a limit on the amount of storage that a VCH can consume. Read more.

Enhancements

vSphere Integrated Containers 1.5.0 includes the following enhancements:

  • Addition of an option to specify an NTP server during deployment of the vSphere Integrated Containers appliance. Read more.
  • New requirement to enter the appliance root password during initialization, reinitialization, and upgrade of the appliance. Read more.
  • Added COMPOSE_TLS_VERSION in the env file that is generated during VCH deployment. Read more.
  • Security and bug fixes listed in Resolved Issues below.

Resolved Issues

No issues that were documented as known issues in previous releases have been fixed in vSphere Integrated Containers appliance 1.5.0. See the resolved issues for each of the vSphere Integrated Containers components:

Known Issues

vSphere Integrated Containers appliance 1.5.0 has the same known issues as v1.4.4.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

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


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

Open Source Components

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

Assets 2
Loading

vSphere Integrated Containers Appliance v1.4.4

31 Oct 14:17
@stuclem stuclem
v1.4.4
0a6da3d
Compare
Choose a tag to compare
vSphere Integrated Containers Appliance v1.4.4

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.4-6375-0a6da3d4.ova

File size: 3342868480
SHA256 checksum: 06131aebed1d2fe4299fb9cefcb18d0bc1f2fba4a700660ce94c43f6735f0d93
SHA1 checksum: 1b9dc717225cb0f02bcc2358176cabac8bdc9222
MD5 checksum: 652ebc88cef35cbe1e22207ef41f9287

This OVA contains the following component versions:

Appliance: https://github.com/vmware/vic-product/archive/v1.4.4.zip 
Engine: https://github.com/vmware/vic/archive/v1.4.3.zip 
Registry: https://github.com/goharbor/harbor/archive/v1.5.4.zip 
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.4.3.zip 
UI: https://github.com/vmware/vic-ui/archive/v1.4.4.zip

Installation and Upgrade

IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or 1.4.4. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client might not work with that version. Only versions 1.4.3 and 1.4.4 have been verified with vSphere 6.7 update 1.

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.

Changes

Full list of changes from 1.4.3.

New Features

vSphere Integrated Containers 1.4.4 includes no new features.

Enhancements

vSphere Integrated Containers 1.4.4 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

There are no resolved issues in the vSphere Integrated Containers appliance in this release. This release includes fixes for issues that are resolved in new versions of vSphere Integrated Containers Registry and the vSphere Integrated Containers UI:

  • vSphere Integrated Containers Registry: Updated Clair to version 2.0.6. This resolves an problem that causes Denial of Service issues with NIST Internet Time Servers getting stuck in a CVE loop. See the Resolved Issues for Harbor 1.5.4.
  • vSphere Integrated Containers UI: Fixes issues in the generated vic-machine command in the Create VCH wizard and a UI deployment issue. See the Resolved Issues for vSphere Integrated Containers UI 1.4.4.

Known Issues

With the exception of the resolved issue above, v1.4.4 has the same known issues as v1.4.3.

View all

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

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


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

Open Source Components

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

Assets 2
Loading