-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
1a080f1
to
d4516b3
Compare
@@ -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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* 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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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"
Signed-off-by: Guillaume Lours <[email protected]>
d4516b3
to
7d48392
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @glours
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