From 8ff1196341539d603dce35c4f1532e5741612181 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1rio=20Serrador?= <61971372+mruiserrmendix@users.noreply.github.com> Date: Fri, 10 Jul 2026 13:32:06 +0200 Subject: [PATCH 1/2] Update Docker Buildpack documentation with alert Add deprecation notice for Docker Buildpacks in the documentation. --- .../on-premises-design/buildpacks/docker-buildpack.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md index de2093d4368..2888530818d 100644 --- a/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md +++ b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md @@ -8,6 +8,9 @@ description: "Describes how to deploy using a Docker image using a Docker Buildp ## Introduction +{{% alert color="warning" %}} With the release of [Mendix Portable Runtime](https://docs.mendix.com/developerportal/deploy/docker-deploy-pad/), we are transitioning away from the Docker Buildpacks toward a modern, container-native approach that packages Mendix applications. As part of this shift, the Docker Buildpack will begin their deprecation journey by not supporting Mendix 12 and future Runtime versions. For more information, see the [blog release](https://www.mendix.com/blog/mendix-portable-runtime/). +{{% /alert %}} + This page explains how to build a Docker image from your Mendix App using a Docker buildpack. Every time you make changes to your app, you must create a new Docker image that can be pushed through the different stages of your application pipeline. This how-to teaches you how to do the following: From 02a070446276c53a7f7a5c4eed5a2d2f224fb1cc Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Fri, 10 Jul 2026 14:33:58 +0200 Subject: [PATCH 2/2] Update docker-buildpack.md --- .../on-premises-design/buildpacks/docker-buildpack.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md index 2888530818d..ce1c9ffda8e 100644 --- a/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md +++ b/content/en/docs/deployment/on-premises-design/buildpacks/docker-buildpack.md @@ -8,7 +8,10 @@ description: "Describes how to deploy using a Docker image using a Docker Buildp ## Introduction -{{% alert color="warning" %}} With the release of [Mendix Portable Runtime](https://docs.mendix.com/developerportal/deploy/docker-deploy-pad/), we are transitioning away from the Docker Buildpacks toward a modern, container-native approach that packages Mendix applications. As part of this shift, the Docker Buildpack will begin their deprecation journey by not supporting Mendix 12 and future Runtime versions. For more information, see the [blog release](https://www.mendix.com/blog/mendix-portable-runtime/). +{{% alert color="warning" %}} +With the release of [Mendix Portable Runtime](https://docs.mendix.com/developerportal/deploy/docker-deploy-pad/), we are transitioning away from the Docker Buildpacks toward a modern, container-native approach that packages Mendix applications. As part of this shift, the Docker Buildpack will begin its deprecation journey by not supporting Mendix 12 and future Runtime versions. + +For more information, see [Mendix Portable Runtime: Deployment, Simplified](https://www.mendix.com/blog/mendix-portable-runtime/). {{% /alert %}} This page explains how to build a Docker image from your Mendix App using a Docker buildpack. Every time you make changes to your app, you must create a new Docker image that can be pushed through the different stages of your application pipeline.