From 622a489ec4d36a58a2528f90fffcf53c8b53c06f Mon Sep 17 00:00:00 2001 From: Nikola Jokic <97525037+nikola-jokic@users.noreply.github.com> Date: Tue, 1 Feb 2022 10:59:58 +0100 Subject: [PATCH 1/2] service containers should not be used in composite actions Explanation that service container should not be used inside the composite actions --- .../using-containerized-services/about-service-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/using-containerized-services/about-service-containers.md b/content/actions/using-containerized-services/about-service-containers.md index 5487cf23f9..001f0b05b1 100644 --- a/content/actions/using-containerized-services/about-service-containers.md +++ b/content/actions/using-containerized-services/about-service-containers.md @@ -23,7 +23,7 @@ topics: Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache. -You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job. +You can configure service containers for each job in a workflow. Service containers are not meant to be used inside composite actions and are not supported to be run inside composite actions. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job. {% data reusables.github-actions.docker-container-os-support %} From 3c28299c08aaadc8a36c7b268cf6dea37711928a Mon Sep 17 00:00:00 2001 From: Lucas Costi Date: Mon, 28 Mar 2022 15:42:48 +1000 Subject: [PATCH 2/2] Update content/actions/using-containerized-services/about-service-containers.md --- .../using-containerized-services/about-service-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/using-containerized-services/about-service-containers.md b/content/actions/using-containerized-services/about-service-containers.md index ec3b989875..bbe88ed928 100644 --- a/content/actions/using-containerized-services/about-service-containers.md +++ b/content/actions/using-containerized-services/about-service-containers.md @@ -23,7 +23,7 @@ topics: Service containers are Docker containers that provide a simple and portable way for you to host services that you might need to test or operate your application in a workflow. For example, your workflow might need to run integration tests that require access to a database and memory cache. -You can configure service containers for each job in a workflow. Service containers are not meant to be used inside composite actions and are not supported to be run inside composite actions. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job. +You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job. However, you cannot create and use service containers inside a composite action. {% data reusables.actions.docker-container-os-support %}