-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Support runtime
in v3.x compose files
#6239
Comments
The lack of runtime selection it is creating many portability problems at Docker build time. See docker/app#241 (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. |
This is likely now OBE given how nvidia has altered nvidia-docker, see #6691 That is... assuming folks were only using |
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. |
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. |
This issue has been automatically closed because it had not recent activity during the stale period. |
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 |
Is there a workaround for this? I'd like to use the runtime parameter to configure specific containers to run with |
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. |
|
PR to support |
Glad to see some progress on this! Specifying |
@leoluk if you try any |
Not sure why this was closed, 1.28 essentially broke this so to speak. We need better documentation on this. Possible related issue |
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. |
I can use "runtime: sysbox-runc" with docker-compose, using "version: 3.8", on debian/bullseye / backports and ubuntu/jammy.
|
By the way, for the people in this thread that might not be aware: The Using Docker Compose V2, with a services:
app:
image: alpine
command: top
runtime: sysbox-runc this option is respected and passed on to the docker daemon. |
Description of the issue
The
runtime
option exists in v2.3, but not v3.x.The text was updated successfully, but these errors were encountered: