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

how to support windows containers #113

Open
lihuiba opened this issue Jul 29, 2022 · 1 comment
Open

how to support windows containers #113

lihuiba opened this issue Jul 29, 2022 · 1 comment

Comments

@lihuiba
Copy link

lihuiba commented Jul 29, 2022

I think there are severval aspects to consider for Windows containers:

  1. porting overlaybd
  • Windows container in Linux host: overlaybd should work out-of-box, by passing through the virtual block device (generated by TCMU in host) to guest; and it's also possible to integrate overlaybd into hypervisor, avoiding the virtual block device in host kernel.

  • Windows container in Windows host: the userspace code of overlaybd can be easily ported to Windows with the help of WSL, cygwin or mingw; but I'm not sure whether WSL have the support for TCMU virtual block device;

  1. snapshotter / graphdriver
  • I believe that windows containers use a different snapshotter / graphdriver than overlay2 in linux, so we have to port overlaybd's driver to windows; as project teleport is also a remote image, which should be a good fit for reference.
  1. building image
  • should work as exepected, as long as using overlaybd's native writable layer;

  • does buildkit have support for windows images?

  1. running container
  • should work as exepected, as long as snapshotter / graphdriver is properly implemented


Any comments?

@lihuiba
Copy link
Author

lihuiba commented Jul 29, 2022

@ganeshkumar5699

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant