From ea41a2228462aa7679edb45990b603a18ffe9905 Mon Sep 17 00:00:00 2001 From: James Stansell Date: Wed, 21 Jun 2023 21:18:15 -0500 Subject: [PATCH] Fix typo in docker compose service connections note See gh-36016 --- .../src/docs/asciidoc/features/docker-compose.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/docker-compose.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/docker-compose.adoc index 8722dd5f4cd..329bfe408e3 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/docker-compose.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/docker-compose.adoc @@ -48,7 +48,7 @@ When doing so, the connection details take precedence over any connection-relate When using Spring Boot’s Docker Compose support, service connections are established to the port mapped by the container. NOTE: Docker compose is usually used in such a way that the ports inside the container are mapped to ephemeral ports on your computer. -For example, A Postgres server may run inside the container using port 5432 but be mapped to a totally different port locally. +For example, a Postgres server may run inside the container using port 5432 but be mapped to a totally different port locally. The service connection will always discover and use the locally mapped port. Service connections are established by using the image name of the container.