Need help with vic-product?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

156 Stars 90 Forks Other 1.2K Commits 137 Opened issues


vSphere Integrated Containers enables VMware customers to deliver a production-ready container solution to their developers and DevOps teams.

Services available


Need anything else?

Contributors list

vSphere Integrated Containers

vSphere Integrated Containers (VIC) is comprised of three main components - the vSphere Integrated Containers Engine, Harbor, and Admiral all of which are available as open source on github.

The VIC Engine is a container runtime for vSphere, allowing developers familiar with Docker to develop in containers and deploy them alongside traditional VM-based workloads on vSphere clusters. These workloads can be managed through the vSphere UI in a way familiar to existing vSphere admins.

Harbor, the enterprise container registry, is an enterprise-class registry server that stores and distributes container images. Harbor extends the open source project Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity and management.

Admiral, the container management portal, provides a UI for developers and app teams to provision and manage containers, including retrieving stats and info about container instances. Cloud administrators will be able to manage container hosts and apply governance to its usage, including capacity quotas and approval workflows. When integrated with vRealize Automation, more advanced capabilities become available, such as deployment blueprints and enterprise-grade Containers-as-a-Service.

With these three capabilities, VIC enables VMware customers to deliver a production ready container solution to their developers and app teams. By leveraging their existing SDDC, customers can now run container-based applications alongside existing virtual machine based workloads in production without having to build out a separate, specialized container infrastructure stack. As an added benefit for customers and partners, VIC is modular. So if your organization already has a container registry in production, you can use that registry with the other components of vSphere Integrated Containers.


See vSphere Integrated Containers in action in this step by step demo


Please refer to the documentation and this video for installing and testing VIC.

Support and Troubleshooting

For general questions, visit the vSphere Integrated Containers Engine channel. If you do not have an or email address, sign up at to get an invitation.

View the VIC Appliance Troubleshooting Guide

Contributing to vSphere Integrated Containers

Contributors and users are encouraged to collaborate using the following resources:

For cross-component or VIC Appliance issues, please use the vic-product Github issue tracker

For issues relating to individual components, please use the component specific Github issue tracker:

VIC Engine




Please refer to for contribution process.


The vic-product components are licensed under Apache 2 with additional licenses denoted within each open source repository (VIC, Admiral, Harbor)

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.