Compose: Support `runtime` in v3.x compose files
Description of the issue
The runtime option exists in v2.3, but not v3.x.
mathstuf
All 15 comments
The lack of runtime selection it is creating many portability problems at Docker build time. See https://github.com/docker/app/issues/241#issuecomment-437362287
bhack
on 9 Nov 2018
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.
xkortex
on 2 Mar 2019
This is likely now OBE given how nvidia has altered nvidia-docker, see #6691
That is... assuming folks were only using runtime for nvidia-docker...
qhaas
on 24 Jul 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.
mathstuf
on 24 Jul 2019
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[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 20 Jan 2020
This issue has been automatically closed because it had not recent activity during the stale period.
stale[bot]
on 27 Jan 2020
Why is it closed?
EscapeLife
on 28 Jan 2020
Why is it closed?
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).
qhaas
on 28 Jan 2020
Why is it closed?
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).
Thanks U
EscapeLife
on 2 Feb 2020
Is there a workaround for this? I'd like to use the runtime parameter to configure specific containers to run with runsc (gVisor).
khimaros
on 21 Apr 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).
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.
robbmue
on 22 Jul 2020
v2 and v3 formats are being merged: https://github.com/docker/compose/pull/7588. This should enable you to use runtime key (for now) in combination with newer features 馃檪
EricHripko
on 22 Jul 2020
PR to support runtime in v3 spec officially: https://github.com/compose-spec/compose-spec/pull/102
AkihiroSuda
on 14 Sep 2020
Glad to see some progress on this! Specifying runtime is a major blocker for us that keeps us on v2.
leoluk
on 14 Sep 2020
@leoluk if you try any 1.27.x release, you will be able to use v2/v3 functionality at the same time (which includes runtime).
EricHripko
on 16 Sep 2020
Related issues
foxx
路
3Comments
AvdN
路
3Comments
bitver
路
3Comments
leiblix
路
3Comments
maltefiala
路
3Comments
Most helpful comment
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.