Skip to content
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 wcow and lcow with wsl2 backend #5067

Closed
kamkie opened this issue Nov 5, 2019 · 7 comments
Closed

support wcow and lcow with wsl2 backend #5067

kamkie opened this issue Nov 5, 2019 · 7 comments

Comments

@kamkie
Copy link

kamkie commented Nov 5, 2019

using wsl2 first preview it was possible tu run lcow container in one context using wsl2 backend
and wcow in another context

new docker desktop on wsl2 preview (2.1.5) currently doesn't allow this

@ebriney
Copy link
Member

ebriney commented Nov 5, 2019

Hi @kamkie , you can still do it but you need to switch to windows containers to start windows daemon or switch to linux containers in windows one in launch at startup.
Only the last daemon is relaunched when you start the application.
And there is only context so you need to switch every time you want to redirect cli to the appropriate engine.

@kamkie
Copy link
Author

kamkie commented Nov 5, 2019

it would be really nice if we could use windows containers and --platform switch (like with wcow and lcow) but with wsl2 backend instead of lcow

if this is something that you don't want to implement fell free to close this issue

@cerebrate
Copy link

I'd like to, shall we say, strongly encourage the implementation of this, or if not this - although it is obviously the preferable option - then at least the ability to run Windows and Linux containers simultaneously and switch back and forth between controlling them using docker context .

Being able to mix container types in a single docker/single machine scenario is the key feature of Docker/WSL 2 for me. If that's not supported, there's not all that much to be gained over my previous practice of installing docker both on Windows and inside WSL.

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@kamkie
Copy link
Author

kamkie commented Feb 4, 2020

can we keep this open?
having lcow and wcow at this same time was nice feature of first preview of docker desktop wsl2

@kamkie
Copy link
Author

kamkie commented May 18, 2020

now tracked in docker/roadmap#79 and #6311

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants