v1.4.1

What's in the Release Notes

• New Features
• Download Binaries
• Installation and Upgrade
• Documentation
• Resolved Issues
• Known Issues
• Open Source Components

New Features

This release provides the following new feature:

• New Built-In Repositories view in vSphere Integrated Containers Management Portal provides better visibility on all repositories that reside in the vSphere Integrated Containers Registry.

Download Binaries

• Official VMware vSphere Integrated Containers 1.4.1 release: http://www.vmware.com/go/download-vic
• Open-source Admiral project: an Admiral container image is available on Docker Hub.

Installation and Upgrade

• For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
• For instructions about how to deploy open-source Admiral, see the Admiral Wiki.

Documentation

• For details on using open-source Admiral, see the Admiral Wiki.
• For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.4/.

Resolved Issues

None at time of writing.

Known Issues

• docker exec always returns 0 and ignores the exit code of processes. vic/#5692
  docker exec always returns 0, even if you specify -it. This issue is potentially due to a delay in vSphere host synchronization. If you configure command-based health checks in vSphere Integrated Containers Management Portal, the health checks are always successful for containers that are provisioned on affected VCHs, even if the user-specified command does not exist in the scope of the container. This is because command-based health checks are considered to be successful if the exit code of that command is 0.

Open Source Components

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