Skip to content
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.

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

add Compose OCI artifact how-to page #22240

Merged
merged 4 commits into from
Mar 17, 2025

Conversation

glours
Copy link
Contributor

@glours glours commented Mar 13, 2025

Description

Add a new Compose how-to page explaining usage OCI artifacts with Compose

Related issues or tickets

https://docker.atlassian.net/browse/APCLI-1015

Reviews

  • Technical review
  • Editorial review
  • Product review

@glours glours requested a review from aevesdocker as a code owner March 13, 2025 10:36
@glours glours self-assigned this Mar 13, 2025
@github-actions github-actions bot added the area/compose Relates to docker-compose.yml spec or docker-compose binary label Mar 13, 2025
Copy link

netlify bot commented Mar 13, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 361ba13
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/67d7f5d2954f600008f1a944
😎 Deploy Preview https://deploy-preview-22240--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@glours glours force-pushed the compose-oci-artifact branch 2 times, most recently from 1a080f1 to d4516b3 Compare March 13, 2025 10:42
@glours glours requested a review from ndeloof March 13, 2025 10:46
@@ -0,0 +1 @@
Docker Compose supports working with OCI (Open Container Initiative) artifacts, allowing you to package and distribute your Compose applications through container registries. This means you can store your Compose files alongside your container images, making it easier to version, share, and deploy your multi-container applications.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Docker Compose supports working with OCI (Open Container Initiative) artifacts, allowing you to package and distribute your Compose applications through container registries. This means you can store your Compose files alongside your container images, making it easier to version, share, and deploy your multi-container applications.
Docker Compose supports working with [OCI artifacts](https://docs.docker.com/docker-hub/repos/manage/hub-images/oci-artifacts/), allowing you to package and distribute your Compose applications through container registries. This means you can store your Compose files alongside your container images, making it easier to version, share, and deploy your multi-container applications.

When you run an application from an OCI artifact, Compose may display warning messages requiring your confirmation to limit risks of running a malicious application:
* Listing the interpolation variables used along with their values
* Listing all environment variables used by the application
* Let you know if your OCI artifact application is using another remote resources (via `include` for example)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Let you know if your OCI artifact application is using another remote resources (via `include` for example)
* Let you know if your OCI artifact application is using another remote resources (via [`include`](/reference/compose-file/include/) for example)

```
or passing multiple Compose files
```bash
$ docker compose -f docker-compose.yml -f docker-compose.override.yml publish username/my-compose-app:latest
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not a good example, as compose + override are the default files being selected when flag is not set.
Also prefer compose.yaml over docker-compose.yml according to the spec

## Limitations and considerations

There is limitations to publishing Compose applications as OCI artifacts:
* You can't publish Compose configuration using `include` of local files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe explain: "if you include another compose model, you should publish this one as well"

@glours glours force-pushed the compose-oci-artifact branch from d4516b3 to 7d48392 Compare March 13, 2025 13:26
Copy link
Contributor

@aevesdocker aevesdocker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @glours

@aevesdocker aevesdocker merged commit 763a789 into docker:main Mar 17, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/compose Relates to docker-compose.yml spec or docker-compose binary
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants