Skip to content

add shortcode #21972

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2025
Merged

add shortcode #21972

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions .../manuals/compose/how-tos/depent-images.md → ...nuals/compose/how-tos/dependent-images.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ title: Build dependent images
weight: 50
---

{{< summary-bar feature_name="Compose dependent images" >}}

To reduce push/pull time and image weight, a common practice for Compose applications is to have services
share base layers as much as possible. You will typically select the same operating system base image for
all services. But you also can get one step further sharing image layers when your images share the same
Expand All @@ -19,7 +21,6 @@ image and install system package `openssl`.
The recommended approach is to group the shared declaration in a single Dockerfile, and use multi-stage features
so that service images are built from this shared declaration.


Dockerfile:

```dockerfile
Expand Down Expand Up @@ -53,7 +54,6 @@ A popular pattern is to reuse a service image as a base image in another service
As Compose does not parse the Dockerfile, it can't automatically detect this dependency
between services to correctly order the build execution.


a.Dockerfile:

```dockerfile
Expand Down Expand Up @@ -82,7 +82,6 @@ services:
dockerfile: b.Dockerfile
```


Legacy Docker Compose v1 used to build images sequentially, which made this pattern usable
out of the box. Compose v2 uses BuildKit to optimise builds and build images in parallel
and requires an explicit declaration.
Expand All @@ -107,7 +106,6 @@ services:
service_a: "service:a"
```


## Build with Bake

Using [Bake](/manuals/build/bake/_index.md) let you pass the complete build definition for all services
Expand Down
4 changes: 3 additions & 1 deletion data/summary.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,10 @@ Compose bridge:
availability: Experimental
Config profiles:
requires: Docker Desktop 4.36 and later
Compose dependent images:
requires: Docker Compose [2.22.0](/manuals/compose/releases/release-notes.md#2220) and later
Compose cgroup:
requires: Docker Compose [2.15.0](/manuals/compose/releases/release-notes.md#2200) and later
requires: Docker Compose [2.15.0](/manuals/compose/releases/release-notes.md#2150) and later
Compose develop:
requires: Docker Compose [2.22.0](/manuals/compose/releases/release-notes.md#2220) and later
Compose driver opts:
Expand Down