Docker Desktop - Compose OCI images run button

[cruizba]

Hello Docker Team!

I just wanted to know if you will support via Docker Desktop to run Docker compose OCI applications via 1-click button? Is it in your road-map?

This would improve a lot the Development Experience of applications which requires docker compose environments to make it easier to get started with complex multi-container environments

BTW, Really cool feature!

Regards

[rimelek (Ákos Takács)]

I checked if this button is available on Docker Hub for docker images and I only saw copy button. I’m not sure how it would be automatically executed in Docker Desktop and how that would be secure as someone could trick me to click on something that runs containers on my machine.

It is just my opinion, but if you think it would be a useful feature, you can rcommend it in the roadmap:

docker/roadmap

You can also check if it is already in it.We can only discuss features and help on the forum, but most of us just community members, so a more direct way to the Docker Staff is through gitHub repositories like the roadmap I linked.

[cruizba]

This is weird. It appears to me in my browser, but only in Linux. In my Windows machine the button does not appear, maybe it is in an experimental phase?

I’m not sure how it would be automatically executed in Docker Desktop and how that would be secure as someone could trick me to click on something that runs containers on my machine.

Yes you may be right, is not the most secure approach, I’m asking because I see this button in multiple places, in the Dockerhub page of any Docker image, and in tags.

A capture of the ubuntu dockerhub image from Chrome in Linux:

[rimelek (Ákos Takács)]

Thanks for the screenshot. I don’t have a Linux Desktop at the moment, but now that you shared it, I remember it. In that case, allowing OCI artifacts would not make a difference so you could ask for it in the roadmap and it is more likely to be implemented than I thought.

[cruizba]

I may ask in the roadmap, thank you! This is not a priority at all. In fact, now that you mention it, running Docker Compose artifacts directly might introduce additional security concerns, since the user running it can’t control how Docker images are executed. That’s different from simply running a Docker image and allowing users to pass in their own parameters (which is what is currently implemented)

At OpenVidu, we’re working to simplify local development of WebRTC applications, which can be overly complex. We believe that by lowering the barrier to entry, more people will want to explore self-hosted platforms like ours.

That said, a command like docker compose -f oci://... up seems simple enough for beginners :).

Thanks anyways!