This topic provides you with an overview of Tanzu Stacks.
Stacks are container images that Tanzu Build Service uses to build and run applications. We provide stacks based on Ubuntu 22.04 (Jammy Jellyfish), 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.
These stacks are based on Ubuntu 22.04 (Jammy Jellyfish) and 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:
We provide a FIPS 140-2 compliant
Bionic Base stack that contains compliant versions of
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).
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 2 business days 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.
Except for the Windows Based Tanzu Buildpack for .NET Framework, all other buildpacks support the Ubuntu 22.04 (Jammy Jellyfish) and Ubuntu 18.04 (Bionic Beaver) stacks.
All Ubuntu 18.04 stacks reach End of General Support on October 31, 2023. Users are advised to migrate to stacks based on Ubuntu 22.04. As of the latest TAP release, Stacks based on Ubuntu 22.04 (Jammy) are the default.
Users should be able to easily upgrade the stack for their apps from Ubuntu Bionic to Ubuntu Jammy stack for those apps that support both platforms. Note that if the underlying language framework itself does not support Ubuntu Jammy, such apps are not supported. .NET 3.1 apps are an example.
A possible issue you may encounter while upgrading apps to a newer stack, is the build platform erroneously reusing the old build cache. If you encounter such issues, try deleting & recreating the workload in TAP, or deleting & recreating the image in TBS.
Tanzu Build Service currently supports the
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
dotnet-frameworkstack, 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
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.
For some versions of the Jammy Full stack before v0.1.72, Jammy Base stack before v0.1.36 and Jammy Tiny stack before v0.1.38, applications that require write permission to the app workspace directory fail with an
operation not permitted error. Please update to the latest versions of Jammy stack if you encounter this issue. Bionic stacks are not affected.
This happens because the build and run images had different user IDs (UIDs), but this has been rectified. Since the above mentioned versions both build and run stack images have the same user ID of 1000.
Originally, different user IDs were set for build and run images as a securtiy tightening effort to prevent files and dependencies installed at build-time from being corrupted at run-time by malicious app code. However, this was found to be disruptive and hence reverted.