Repository navigation
Support runtime in v3.x compose files #6239
Description
Description of the issue
The runtime option exists in v2.3, but not v3.x.
Reacted by bhack, grim13b, Collins Abitekaniza, Dennis O'Brien, Takuma Shiotsu, Jake Poznanski, Ohad Lahav, Duc Bui, Alex Sergeev, Timur and 40 more
Reacted by bhack and Collins Abitekaniza
Reacted by Loreto Parisi, Krzysiek, Hekui Guo and rodrickcui
Activity
bhack commentedon Nov 9, 2018
The lack of runtime selection it is creating many portability problems at Docker build time. See docker-archive-public/docker.app#241 (comment)
xkortex commentedon Mar 2, 2019
I am not particular how it is implemented, but I would really appreciate using compose v3.X with CUDA GPU containers. My current choice is either DC.yml v2.X files, or Makefiles.
qhaas commentedon Jul 24, 2019
This is likely now OBE given how nvidia has altered nvidia-docker, see #6691
That is... assuming folks were only using
runtimefor nvidia-docker...mathstuf commentedon Jul 24, 2019
I was interested in it for OCI hooks personally, but have ended up not going with docker-compose anyways, so this sort of fell off my plate. Guidance for continuing this is over on #6240.
stale commentedon Jan 20, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Jan 27, 2020
This issue has been automatically closed because it had not recent activity during the stale period.
EscapeLife commentedon Jan 28, 2020
Why is it closed?
qhaas commentedon Jan 28, 2020
Most of the discussion has moved to #6691 since the API changed with newer versions of docker/nvidia-docker, breaking even v2.3 (without adding deprecated/legacy packages).
EscapeLife commentedon Feb 2, 2020
Thanks U
khimaros commentedon Apr 21, 2020
Is there a workaround for this? I'd like to use the runtime parameter to configure specific containers to run with
runsc(gVisor).robbmue commentedon Jul 22, 2020
But what if i want to use another runtime in my docker-compose files? I e.g. am trying to use Kata as my runtime, but would like to use features from v3.x as well. Am stuck with v2.3 to set my runtimes.
EricHripko commentedon Jul 22, 2020
v2andv3formats are being merged: #7588. This should enable you to useruntimekey (for now) in combination with newer features 🙂AkihiroSuda commentedon Sep 14, 2020
PR to support
runtimein v3 spec officially: compose-spec/compose-spec#102leoluk commentedon Sep 14, 2020
Glad to see some progress on this! Specifying
runtimeis a major blocker for us that keeps us on v2.EricHripko commentedon Sep 16, 2020
@leoluk if you try any
1.27.xrelease, you will be able to use v2/v3 functionality at the same time (which includesruntime).Motophan commentedon Feb 8, 2021
#8107
Not sure why this was closed, 1.28 essentially broke this so to speak. We need better documentation on this. Possible related issue
mathstuf commentedon Feb 9, 2021
It was closed due to a stalebot (something I, personally, find to be of dubious utility on issues). No idea if upstream actually looks at closed issues with any interest to undo such decisions.
mqu commentedon Sep 20, 2022
I can use "runtime: sysbox-runc" with docker-compose, using "version: 3.8", on debian/bullseye / backports and ubuntu/jammy.
apt install -t bullseye-backports docker-composelaurazard commentedon Sep 20, 2022
By the way, for the people in this thread that might not be aware:
The
runtimeservice-level key is supported (as documented here) by the Compose Specification (here).Using Docker Compose V2, with a
compose.yamlthat omits theversiontop-level key such as:this option is respected and passed on to the docker daemon.