You should be able to build a kernel module and add it with a sufficiently privileged container.

And I was hitting Couldnt set tty to PPP discipline: Invalid argument error after strictly following Debian HOWTO.

Then I desperately tried to build and run the container under ubuntu host and the issue wasnt present.

But unfortunately this is probably not all what is required.

Your project files should be stored within your WSL 2 distro of choice, you should run the docker CLI from this distro, and you should avoid accessing files stored on the Windows host as much as possible.

They just run in separate namespaces so that they have the illusion of running totally independently.

Docker Desktop leverages that to handle bind mounts from a WSL 2 distro without involving any remote file sharing system.

This means that when you mount your project files in a container (with docker run -v my-project:sources ), docker will propagate inotify events and share the same cache as your own distro to avoid reading file content from disk repeatedly.

Those scripts are often developed for Linux first (because most of the time, CICD pipelines for those projects run on Linux), and developers running on Windows are often considered second-class citizens.

They are often using less polished versions of those scripts, and have to deal with subtle behavioral differences.

This means that Windows-specific scripts dont need to be maintained anymore.

Also, that means that you wont experience issues with different line endings between Windows and MacLinux users.

Visual Studio Code architecture is based on a clientserver approach where pretty much everything except rendering and input processing is done in a server process, while the UI itself runs in a client process.

Remote to WSL leverages that to run the whole server process within WSL while the UI runs as a classic win32 process.

For example, if I have a project in my Ubuntu distro at wall-e, I can access it from Windows Explorer (and from any Windows Process) via the special network share wslUbuntuhomesimonwall-e.

To leverage this as much as possible (and also to get access to the latest build features), you should enable BuildKit by default.

This is awesome for most cases, but there is a category of workloads where this can cause issues.

Docker provides a way to impose limits in allocatable memory (as well as quotas on CPU usage) by a container.

However, if the kernel decides to keep content in cache (and with Docker, it tends to happen quite a lot), the amount of memory reclaimed might not be sufficient.

Docker For Mac Kernel