Repository navigation
Feature request: Add necessary support for new functionality(introduce volume.type=image) from compose-spec #4767
Description
Activity
- changed the title
[-]Add necessary support for new functionality(image volume was introduced in v2.35.0) from compose-spec[/-][+]Feature request: Add necessary support for new functionality(introduce volume.type=image) from compose-spec[/+]on Mar 3, 2026 Apparently OCI Artifact volume mount support is not as wide spread as OCI image volume mount.
talked about in: containerd/containerd#11381
CRI-O has added basic OCI Artifact volume mount support, utilizing the same type: mount.image as for OCI Image, the runtime investigates the details of the pulled OCI and handles it accordingly: cri-o/cri-o#8953
KEP-4639 talks about OCI Objects as a term including both OCI Images and OCI Artifacts: kubernetes/enhancements#4639 and feature now GA: kubernetes/kubernetes#136711Hi, I’d like to work on this. nerdctl run --mount type=image landed in #4990, while image-subpath support is currently in #4993. My plan is to translate Compose image volumes into --mount type=image,... arguments in serviceparser, support image.subpath, and add unit and integration tests. Would you prefer that I prepare this as a stacked change on #4993, or wait until #4993 is merged?
Reacted by KristoferHansson
What is the problem you're trying to solve
This is a feature request for adding necessary support in nerdctl for new additions to the compose spec related to
OCI image/artifact volume mount
Compose spec commit:
"introduce volume.type=image"
compose-spec/compose-spec@40af7cd
merged docker compose pull request supporting the above compose feature addition
docker/compose#12725
closed podman-compose issue and referenced merged pull request for supporting the above compose feature addition
containers/podman-compose#1202
/Kristofer