Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

vic_v1.3.0
Compare
Choose a tag to compare
@martin-borisov martin-borisov released this 04 Jan 15:44
vic_v1.3.0
df24e72

Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.3.0

New Features

This release provides the following new features and enhancements:

  • vSphere Integrated Containers Management Portal now uses the Docker Events REST API to display the status of containers and hosts as close as possible to the status reported by the underlying hosts.
  • vSphere Integrated Containers Management Portal now supports VCH container network definitions with the --container-network-ip-range in a non-CIDR format. For more information, see Configure Container Networks.

Resolved Issues

The following issues found in previous versions have been fixed in 1.3.0:

  • Spawning container using container networks may fail when using VCH. #228
    In some cases the VCH where the container is being provisioned, for some reason, returns a very big response (>10MB) when doing an INSPECT on that just provisioned container. And since Admiral expects a relatively small answer (<32KB) that big response can't be stored. The problematic part of the big response is the HostConfig.PortBindings section, because it includes all the system ports with an actual empty configuration. The fix consist of ignoring all the useless system ports in the Admiral side, unless until the issue is fixed in the VCH side.
  • Admiral UI failed to load a particular user (or group) when there are many users (or groups) on PSC #225
    When having available more than 100 users that start with the same prefix (e.g. user1, user10, user11, user100, user101, user1000, etc.), it may happen that when searching for a particular user (e.g. user1) the response from PSC does not contain the desired one. The fix consist of adding to the list of matching users and groups returned by PSC also the exact match of the search criteria if it's an actual user or group.
  • Admiral's containers page loads slowly #219
    When having a large amount of containers, scrolling down the Container page keeps refreshing and loads new content pretty slowly.
  • Project rename breaks Harbor registry functionalities #218
    The project name cannot be renamed as the repository was stored in the default registry (Harbor) with the project name.

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.

Download Binaries

Installation

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