Runwasi is suitable and enabled by default #47604
-
Currently, when using Docker for WASI runtime, it is necessary to enable configuration and download the corresponding runWASI runtime yourself.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I see you are repeating your question from #46550 (comment), more-or-less. To reiterate and clarify, of course the feature will be on by default when it is stable. We would like to do so in a major version or two, though the timeline is not definite and it's definitely a "when it's ready" change as it is high-risk and quite invasive. #47526 and follow-ups are very likely prerequisites as well. Regarding Wasm runtimes/shims, that is not a moby/moby question. While we may add Wasm runtimes to the development environment/integration tests, pre-installing runtimes is a question for downstream packagers. For example, Docker CE packaging is at https://github.com/docker/docker-ce-packaging; the code there is what governs what is in packages from https://download.docker.com, and decisions to package (or not package) runtimes are made in that downstream project. |
Beta Was this translation helpful? Give feedback.
I see you are repeating your question from #46550 (comment), more-or-less.
To reiterate and clarify, of course the feature will be on by default when it is stable. We would like to do so in a major version or two, though the timeline is not definite and it's definitely a "when it's ready" change as it is high-risk and quite invasive. #47526 and follow-ups are very likely prerequisites as well.
Regarding Wasm runtimes/shims, that is not a moby/moby question. While we may add Wasm runtimes to the development environment/integration tests, pre-installing runtimes is a question for downstream packagers. For example, Docker CE packaging is at https://github.com/docker/docker-ce-packaging; the …