This topic provides an overview of Tanzu Stacks.

Overview

Stacks are container images that Tanzu Build Service uses to build and run applications. We provide stacks based on Ubuntu 18.04 (Bionic Beaver), and Microsoft Windows Server Core LTSC 2019 with different use cases shown below.

Stack images are published to the Tanzu Network Registry. You can download stack images from the VMware Tanzu Network

Ubuntu Stacks

These stacks are based on Ubuntu 18.04 (Bionic Beaver) Ubuntu is an open-source Linux distribution published by Canonical, who also provides commercial support and security updates.

The following Ubuntu stacks are supported in Tanzu Build Service:

  • tiny
  • base
    • Java apps and .NET Core apps
    • Go apps that require some C libraries
    • Node.js, Python, or Ruby apps without many native extensions
  • full
    • PHP, Node.js, Python, or Ruby apps with many native extensions

Security and Hardening Features

  • By using Ubuntu 18.04 as the base image for our stacks, we benefit from all of the security provided by Canonical and Ubuntu. For more information, see the Canonical web site and the Ubuntu wiki.
  • Our automatic monitoring and patching of CVEs means that our stacks are often updated within hours of Canonical's patches.
  • The stack images are run as a dedicated non-root user when building and running applications.
  • Each stack image has detailed metadata describing the image's components, such as the base operating system and packages.
  • Each stack has separate images for building and running applications. The packages on the runtime image are curated to exclude compilers and other tools that might pose security risks.

For the source code, see stacks on GitHub.

FIPS Compliance

We provide a FIPS 140-2 compliant base stack that contains compliant versions of libssl and openssl. To download the FIPS 140-2 compliant stack, see VMware Tanzu Network.

Note: Access to the FIPS 140-2 compliant stack tile is restricted. To request access, reach out to your Tanzu account representative.

For more information about FIPS compliance, see Compliance FAQs: Federal Information Processing Standards (FIPS).

Stack Updates

Stacks are rebuilt whenever a package is patched to fix a CVE. For more information about CVEs, see Common Vulnerabilities and Exposures (CVE). Stacks are also rebuilt weekly to ensure packages without CVEs are also up to date.

We aim to release stack updates that fix High and Critical CVEs within 48 hours of the patch release. For stack updates fixing Low and Medium CVEs, we aim to release within two weeks.

Note: Security scanning tools might report vulnerabilities in apps even when using the latest stack. This can occur when a CVE patch is not yet available upstream or if Canonical determines that the vulnerability is not severe enough to fix.

Stacks are backwards compatible. A stack can safely be upgraded to the most recent version within the major version line. If for some reason backwards compatibility is broken, it happens when a new major version is released.

Stack updates in Tanzu Build Service are efficient and do not break applications. When a stack is updated, each application that uses that stack is rebased on top of the new stack image. The application does not need to be rebuilt because the stack maintains application binary interface (ABI) compatibility.

Microsoft Windows Stacks

Tanzu Build Service currently supports the dotnet-framework stack.

  • dotnet-framework)
    • .NET Framework applications
    • .NET Core apps that have dependencies on the Windows Operating System

This stack is based on Microsoft Windows Server Core LTSC 2019

For this stack, see VMware Tanzu Stack Image for .NET Framework on Microsoft Windows Server Core

Security and Hardening Features

  • By using Microsoft Windows Server Core LTSC 2019 as the base image for the dotnet-framework stack, we benefit from all of the security provided by Microsoft. For more information, see Microsoft's web site on its Server Core 2019 LTSC image
  • The stack images are run as a dedicated non-Administrator user when running applications
  • Each stack image has detailed metadata describing the image’s components, such as the base operating system and packages.
  • Each stack has separate images for building and running applications. The packages on the runtime image are curated to exclude compilers and other tools that might pose security risks.

Scope of Support

VMware Support can assist in troubleshooting issues encountered using any of the stacks that are shipped as a part of Tanzu Build Service.

As detailed in Security and Hardening Features above, all stack images shipped within Tanzu Build Service are patched in response to upstream CVEs after they are patched by Canonical.

For more information about what Tanzu Build Service supports, see Scope of Support for Cloud Native Buildpacks.

check-circle-line exclamation-circle-line close-line
Scroll to top icon