{"title":"","byline":"dockur","dir":null,"lang":null,"content":"
\n

Windows inside a Docker container.

\n

Features āœØ

\n
    \n
  • ISO downloader
    • \n
  • KVM acceleration
    • \n
  • Web-based viewer
    • \n
\n

Video šŸ“ŗ

\n

\"Youtube\"

\n

Usage šŸ³

\n

Via Docker Compose:

\n
services:\n  windows:\n    image: dockurr/windows\n    container_name: windows\n    environment:\n      VERSION: \"11\"\n    devices:\n      - /dev/kvm\n    cap_add:\n      - NET_ADMIN\n    ports:\n      - 8006:8006\n      - 3389:3389/tcp\n      - 3389:3389/udp\n    stop_grace_period: 2m
\n

Via Docker CLI:

\n
docker run -it --rm -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 dockurr/windows
\n

Via Kubernetes:

\n
kubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/master/kubernetes.yml
\n

Compatibility āš™ļø

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ProductPlatform
Docker EngineLinuxāœ…
Docker DesktopLinuxāŒ
Docker DesktopmacOSāŒ
Docker DesktopWindows 11āœ…
Docker DesktopWindows 10āŒ
\n

FAQ šŸ’¬

\n

How do I use it?

\n

Very simple! These are the steps:

\n
    \n
  • \n

    Start the container and connect to port 8006 using your web browser.

    \n
    • \n
  • \n

    Sit back and relax while the magic happens, the whole installation will be performed fully automatic.

    \n
    • \n
  • \n

    Once you see the desktop, your Windows installation is ready for use.

    \n
    • \n
\n

Enjoy your brand new machine, and don't forget to star this repo!

\n

How do I select the Windows version?

\n

By default, Windows 11 will be installed. But you can add the VERSION environment variable to your compose file, in order to specify an alternative Windows version to be downloaded:

\n
environment:\n  VERSION: \"11\"
\n

Select from the values below:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ValueVersionSize
11Windows 11 Pro5.4 GB
11lWindows 11 LTSC4.2 GB
11eWindows 11 Enterprise5.8 GB
10Windows 10 Pro5.7 GB
10lWindows 10 LTSC4.6 GB
10eWindows 10 Enterprise5.2 GB
8eWindows 8.1 Enterprise3.7 GB
7eWindows 7 Enterprise3.0 GB
veWindows Vista Enterprise3.0 GB
xpWindows XP Professional0.6 GB
2025Windows Server 20255.0 GB
2022Windows Server 20224.7 GB
2019Windows Server 20195.3 GB
2016Windows Server 20166.5 GB
2012Windows Server 20124.3 GB
2008Windows Server 20083.0 GB
2003Windows Server 20030.6 GB
\n\n

How do I change the storage location?

\n

To change the storage location, include the following bind mount in your compose file:

\n
volumes:\n  - /var/win:/storage
\n

Replace the example path /var/win with the desired storage folder.

\n

How do I change the size of the disk?

\n

To expand the default size of 64 GB, add the DISK_SIZE setting to your compose file and set it to your preferred capacity:

\n
environment:\n  DISK_SIZE: \"256G\"
\n

Tip

This can also be used to resize the existing disk to a larger capacity without any data loss.

\n
\n

How do I share files with the host?

\n

Open 'File Explorer' and click on the 'Network' section, you will see a computer called host.lan. Double-click it and it will show a folder called Data, which can be bound to any folder on your host via the compose file:

\n
volumes:\n  -  /home/user/example:/data
\n

The example folder /home/user/example will be available as \\\\host.lan\\Data.

\n

Tip

You can map this path to a drive letter in Windows, for easier access.

\n
\n

How do I install a custom image?

\n

In order to download an unsupported ISO image that is not selectable from the list above, specify the URL of that ISO in the VERSION environment variable, for example:

\n
environment:\n  VERSION: \"https://example.com/win.iso\"
\n

Alternatively, you can also skip the download and use a local file instead, by binding it in your compose file in this way:

\n
volumes:\n  - /home/user/example.iso:/custom.iso
\n

Replace the example path /home/user/example.iso with the filename of your desired ISO file, the value of VERSION will be ignored in this case.

\n

How do I run a script after installation?

\n

To run your own script after installation, you can create a file called install.bat and place it in a folder together with any additional files it needs (software to be installed for example). Then bind that folder in your compose file like this:

\n
volumes:\n  -  /home/user/example:/oem
\n

The example folder /home/user/example will be copied to C:\\OEM during installation and the containing install.bat will be executed during the last step.

\n

How do I perform a manual installation?

\n

It's best to stick to the automatic installation, as it adjusts various settings to prevent common issues when running Windows inside a virtual environment.

\n

However, if you insist on performing the installation manually, add the following environment variable to your compose file:

\n\n

How do I change the amount of CPU or RAM?

\n

By default, the container will be allowed to use a maximum of 2 CPU cores and 4 GB of RAM.

\n

If you want to adjust this, you can specify the desired amount using the following environment variables:

\n
environment:\n  RAM_SIZE: \"8G\"\n  CPU_CORES: \"4\"
\n

How do I configure the username and password?

\n

By default, a user called Docker is created during the installation, with an empty password.

\n

If you want to use different credentials, you can change them in your compose file:

\n
environment:\n  USERNAME: \"bill\"\n  PASSWORD: \"gates\"
\n

How do I select the Windows language?

\n

By default, the English version of Windows will be downloaded. But you can add the LANGUAGE environment variable to your compose file, in order to specify an alternative language:

\n
environment:\n  LANGUAGE: \"French\"
\n

You can choose between: šŸ‡¦šŸ‡Ŗ Arabic, šŸ‡§šŸ‡¬ Bulgarian, šŸ‡ØšŸ‡³ Chinese, šŸ‡­šŸ‡· Croatian, šŸ‡ØšŸ‡æ Czech, šŸ‡©šŸ‡° Danish, šŸ‡³šŸ‡± Dutch, šŸ‡¬šŸ‡§ English, šŸ‡ŖšŸ‡Ŗ Estonian, šŸ‡«šŸ‡® Finnish, šŸ‡«šŸ‡· French, šŸ‡©šŸ‡Ŗ German, šŸ‡¬šŸ‡· Greek, šŸ‡®šŸ‡± Hebrew, šŸ‡­šŸ‡ŗ Hungarian, šŸ‡®šŸ‡¹ Italian, šŸ‡ÆšŸ‡µ Japanese, šŸ‡°šŸ‡· Korean, šŸ‡±šŸ‡» Latvian, šŸ‡±šŸ‡¹ Lithuanian, šŸ‡³šŸ‡“ Norwegian, šŸ‡µšŸ‡± Polish, šŸ‡µšŸ‡¹ Portuguese, šŸ‡·šŸ‡“ Romanian, šŸ‡·šŸ‡ŗ Russian, šŸ‡·šŸ‡ø Serbian, šŸ‡øšŸ‡° Slovak, šŸ‡øšŸ‡® Slovenian, šŸ‡ŖšŸ‡ø Spanish, šŸ‡øšŸ‡Ŗ Swedish, šŸ‡¹šŸ‡­ Thai, šŸ‡¹šŸ‡· Turkish and šŸ‡ŗšŸ‡¦ Ukrainian.

\n

How do I select the keyboard layout?

\n

If you want to use a keyboard layout or locale that is not the default for your selected language, you can add the KEYBOARD and REGION variables with a culture code, like this:

\n
environment:\n  REGION: \"en-US\"\n  KEYBOARD: \"en-US\"
\n

Note

Changing these values will have no effect after the installation has been performed already. Use the control panel inside Windows in that case.

\n
\n

How do I connect using RDP?

\n

The web-viewer is mainly meant to be used during installation, as its picture quality is low, and it has no audio or clipboard for example.

\n

So for a better experience you can connect using any Microsoft Remote Desktop client to the IP of the container, using the username Docker and by leaving the password empty.

\n

There is a RDP client for Android available from the Play Store and one for iOS in the Apple Store. For Linux you can use FreeRDP and on Windows just type mstsc in the search box.

\n

How do I assign an individual IP address to the container?

\n

By default, the container uses bridge networking, which shares the IP address with the host.

\n

If you want to assign an individual IP address to the container, you can create a macvlan network as follows:

\n
docker network create -d macvlan \\\n    --subnet=192.168.0.0/24 \\\n    --gateway=192.168.0.1 \\\n    --ip-range=192.168.0.100/28 \\\n    -o parent=eth0 vlan
\n

Be sure to modify these values to match your local subnet.

\n

Once you have created the network, change your compose file to look as follows:

\n
services:\n  windows:\n    container_name: windows\n    ..<snip>..\n    networks:\n      vlan:\n        ipv4_address: 192.168.0.100\n\nnetworks:\n  vlan:\n    external: true
\n

An added benefit of this approach is that you won't have to perform any port mapping anymore, since all ports will be exposed by default.

\n

Important

This IP address won't be accessible from the Docker host due to the design of macvlan, which doesn't permit communication between the two. If this is a concern, you need to create a second macvlan as a workaround.

\n
\n

How can Windows acquire an IP address from my router?

\n

After configuring the container for macvlan, it is possible for Windows to become part of your home network by requesting an IP from your router, just like a real PC.

\n

To enable this mode, add the following lines to your compose file:

\n
environment:\n  DHCP: \"Y\"\ndevices:\n  - /dev/vhost-net\ndevice_cgroup_rules:\n  - 'c *:* rwm'
\n

Note

In this mode, the container and Windows will each have their own separate IPs.

\n
\n

How do I add multiple disks?

\n

To create additional disks, modify your compose file like this:

\n
environment:\n  DISK2_SIZE: \"32G\"\n  DISK3_SIZE: \"64G\"\nvolumes:\n  - /home/example:/storage2\n  - /mnt/data/example:/storage3
\n

How do I pass-through a disk?

\n

It is possible to pass-through disk devices directly by adding them to your compose file in this way:

\n
devices:\n  - /dev/sdb:/disk1\n  - /dev/sdc:/disk2
\n

Use /disk1 if you want it to become your main drive (which will be formatted during installation), and use /disk2 and higher to add them as secondary drives (which will stay untouched).

\n

How do I pass-through a USB device?

\n

To pass-through a USB device, first lookup its vendor and product id via the lsusb command, then add them to your compose file like this:

\n
environment:\n  ARGUMENTS: \"-device usb-host,vendorid=0x1234,productid=0x1234\"\ndevices:\n  - /dev/bus/usb
\n

Important

If the device is a USB disk drive, please wait until after the installation is completed before connecting it. Otherwise the installation may fail, as the order of the disks can get rearranged.

\n
\n

How do I verify if my system supports KVM?

\n

Only Linux and Windows 11 support KVM virtualization, macOS and Windows 10 do not unfortunately.

\n

You can run the following commands in Linux to check your system:

\n
sudo apt install cpu-checker\nsudo kvm-ok
\n

If you receive an error from kvm-ok indicating that KVM cannot be used, please check whether:

\n
    \n
  • \n

    the virtualization extensions (Intel VT-x or AMD SVM) are enabled in your BIOS.

    \n
    • \n
  • \n

    you enabled \"nested virtualization\" if you are running the container inside a virtual machine.

    \n
    • \n
  • \n

    you are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's.

    \n
    • \n
\n

If you do not receive any error from kvm-ok but the container still complains about KVM, please check whether:

\n
    \n
  • \n

    you are not using \"Docker Desktop for Linux\" as it does not support KVM, instead make use of Docker Engine directly.

    \n
    • \n
  • \n

    it could help to add privileged: true to your compose file (or sudo to your docker run command), to rule out any permission issue.

    \n
    • \n
\n

How do I run macOS in a container?

\n

You can use dockur/macos for that. It shares many of the same features, except for the automatic installation.

\n

Is this project legal?

\n

Yes, this project contains only open-source code and does not distribute any copyrighted material. Any product keys found in the code are just generic placeholders provided by Microsoft for trial purposes. So under all applicable laws, this project will be considered legal.

\n

Stars šŸŒŸ

\n

\"Stars\"

\n

Disclaimer āš–ļø

\n

The product names, logos, brands, and other trademarks referred to within this project are the property of their respective trademark holders. This project is not affiliated, sponsored, or endorsed by Microsoft Corporation.

\n
","textContent":"\nWindows inside a Docker container.\nFeatures āœØ\n\nISO downloader\nKVM acceleration\nWeb-based viewer\n\nVideo šŸ“ŗ\n\nUsage šŸ³\nVia Docker Compose:\nservices:\n windows:\n image: dockurr/windows\n container_name: windows\n environment:\n VERSION: \"11\"\n devices:\n - /dev/kvm\n cap_add:\n - NET_ADMIN\n ports:\n - 8006:8006\n - 3389:3389/tcp\n - 3389:3389/udp\n stop_grace_period: 2m\nVia Docker CLI:\ndocker run -it --rm -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 dockurr/windows\nVia Kubernetes:\nkubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/master/kubernetes.yml\nCompatibility āš™ļø\n\n\n\nProduct\nPlatform\n\n\n\n\n\nDocker Engine\nLinux\nāœ…\n\n\nDocker Desktop\nLinux\nāŒ\n\n\nDocker Desktop\nmacOS\nāŒ\n\n\nDocker Desktop\nWindows 11\nāœ…\n\n\nDocker Desktop\nWindows 10\nāŒ\n\n\n\nFAQ šŸ’¬\nHow do I use it?\nVery simple! These are the steps:\n\n\nStart the container and connect to port 8006 using your web browser.\n\n\nSit back and relax while the magic happens, the whole installation will be performed fully automatic.\n\n\nOnce you see the desktop, your Windows installation is ready for use.\n\n\nEnjoy your brand new machine, and don't forget to star this repo!\nHow do I select the Windows version?\nBy default, Windows 11 will be installed. But you can add the VERSION environment variable to your compose file, in order to specify an alternative Windows version to be downloaded:\nenvironment:\n VERSION: \"11\"\nSelect from the values below:\n\n\n\nValue\nVersion\nSize\n\n\n\n\n11\nWindows 11 Pro\n5.4 GB\n\n\n11l\nWindows 11 LTSC\n4.2 GB\n\n\n11e\nWindows 11 Enterprise\n5.8 GB\n\n\n\n\n\n\n\n10\nWindows 10 Pro\n5.7 GB\n\n\n10l\nWindows 10 LTSC\n4.6 GB\n\n\n10e\nWindows 10 Enterprise\n5.2 GB\n\n\n\n\n\n\n\n8e\nWindows 8.1 Enterprise\n3.7 GB\n\n\n7e\nWindows 7 Enterprise\n3.0 GB\n\n\nve\nWindows Vista Enterprise\n3.0 GB\n\n\nxp\nWindows XP Professional\n0.6 GB\n\n\n\n\n\n\n\n2025\nWindows Server 2025\n5.0 GB\n\n\n2022\nWindows Server 2022\n4.7 GB\n\n\n2019\nWindows Server 2019\n5.3 GB\n\n\n2016\nWindows Server 2016\n6.5 GB\n\n\n2012\nWindows Server 2012\n4.3 GB\n\n\n2008\nWindows Server 2008\n3.0 GB\n\n\n2003\nWindows Server 2003\n0.6 GB\n\n\n\n\nHow do I change the storage location?\nTo change the storage location, include the following bind mount in your compose file:\nvolumes:\n - /var/win:/storage\nReplace the example path /var/win with the desired storage folder.\nHow do I change the size of the disk?\nTo expand the default size of 64 GB, add the DISK_SIZE setting to your compose file and set it to your preferred capacity:\nenvironment:\n DISK_SIZE: \"256G\"\nTipThis can also be used to resize the existing disk to a larger capacity without any data loss.\n\nHow do I share files with the host?\nOpen 'File Explorer' and click on the 'Network' section, you will see a computer called host.lan. Double-click it and it will show a folder called Data, which can be bound to any folder on your host via the compose file:\nvolumes:\n - /home/user/example:/data\nThe example folder /home/user/example will be available as \\\\host.lan\\Data.\nTipYou can map this path to a drive letter in Windows, for easier access.\n\nHow do I install a custom image?\nIn order to download an unsupported ISO image that is not selectable from the list above, specify the URL of that ISO in the VERSION environment variable, for example:\nenvironment:\n VERSION: \"https://example.com/win.iso\"\nAlternatively, you can also skip the download and use a local file instead, by binding it in your compose file in this way:\nvolumes:\n - /home/user/example.iso:/custom.iso\nReplace the example path /home/user/example.iso with the filename of your desired ISO file, the value of VERSION will be ignored in this case.\nHow do I run a script after installation?\nTo run your own script after installation, you can create a file called install.bat and place it in a folder together with any additional files it needs (software to be installed for example). Then bind that folder in your compose file like this:\nvolumes:\n - /home/user/example:/oem\nThe example folder /home/user/example will be copied to C:\\OEM during installation and the containing install.bat will be executed during the last step.\nHow do I perform a manual installation?\nIt's best to stick to the automatic installation, as it adjusts various settings to prevent common issues when running Windows inside a virtual environment.\nHowever, if you insist on performing the installation manually, add the following environment variable to your compose file:\n\nHow do I change the amount of CPU or RAM?\nBy default, the container will be allowed to use a maximum of 2 CPU cores and 4 GB of RAM.\nIf you want to adjust this, you can specify the desired amount using the following environment variables:\nenvironment:\n RAM_SIZE: \"8G\"\n CPU_CORES: \"4\"\nHow do I configure the username and password?\nBy default, a user called Docker is created during the installation, with an empty password.\nIf you want to use different credentials, you can change them in your compose file:\nenvironment:\n USERNAME: \"bill\"\n PASSWORD: \"gates\"\nHow do I select the Windows language?\nBy default, the English version of Windows will be downloaded. But you can add the LANGUAGE environment variable to your compose file, in order to specify an alternative language:\nenvironment:\n LANGUAGE: \"French\"\nYou can choose between: šŸ‡¦šŸ‡Ŗ Arabic, šŸ‡§šŸ‡¬ Bulgarian, šŸ‡ØšŸ‡³ Chinese, šŸ‡­šŸ‡· Croatian, šŸ‡ØšŸ‡æ Czech, šŸ‡©šŸ‡° Danish, šŸ‡³šŸ‡± Dutch, šŸ‡¬šŸ‡§ English, šŸ‡ŖšŸ‡Ŗ Estonian, šŸ‡«šŸ‡® Finnish, šŸ‡«šŸ‡· French, šŸ‡©šŸ‡Ŗ German, šŸ‡¬šŸ‡· Greek, šŸ‡®šŸ‡± Hebrew, šŸ‡­šŸ‡ŗ Hungarian, šŸ‡®šŸ‡¹ Italian, šŸ‡ÆšŸ‡µ Japanese, šŸ‡°šŸ‡· Korean, šŸ‡±šŸ‡» Latvian, šŸ‡±šŸ‡¹ Lithuanian, šŸ‡³šŸ‡“ Norwegian, šŸ‡µšŸ‡± Polish, šŸ‡µšŸ‡¹ Portuguese, šŸ‡·šŸ‡“ Romanian, šŸ‡·šŸ‡ŗ Russian, šŸ‡·šŸ‡ø Serbian, šŸ‡øšŸ‡° Slovak, šŸ‡øšŸ‡® Slovenian, šŸ‡ŖšŸ‡ø Spanish, šŸ‡øšŸ‡Ŗ Swedish, šŸ‡¹šŸ‡­ Thai, šŸ‡¹šŸ‡· Turkish and šŸ‡ŗšŸ‡¦ Ukrainian.\nHow do I select the keyboard layout?\nIf you want to use a keyboard layout or locale that is not the default for your selected language, you can add the KEYBOARD and REGION variables with a culture code, like this:\nenvironment:\n REGION: \"en-US\"\n KEYBOARD: \"en-US\"\nNoteChanging these values will have no effect after the installation has been performed already. Use the control panel inside Windows in that case.\n\nHow do I connect using RDP?\nThe web-viewer is mainly meant to be used during installation, as its picture quality is low, and it has no audio or clipboard for example.\nSo for a better experience you can connect using any Microsoft Remote Desktop client to the IP of the container, using the username Docker and by leaving the password empty.\nThere is a RDP client for Android available from the Play Store and one for iOS in the Apple Store. For Linux you can use FreeRDP and on Windows just type mstsc in the search box.\nHow do I assign an individual IP address to the container?\nBy default, the container uses bridge networking, which shares the IP address with the host.\nIf you want to assign an individual IP address to the container, you can create a macvlan network as follows:\ndocker network create -d macvlan \\\n --subnet=192.168.0.0/24 \\\n --gateway=192.168.0.1 \\\n --ip-range=192.168.0.100/28 \\\n -o parent=eth0 vlan\nBe sure to modify these values to match your local subnet.\nOnce you have created the network, change your compose file to look as follows:\nservices:\n windows:\n container_name: windows\n ....\n networks:\n vlan:\n ipv4_address: 192.168.0.100\n\nnetworks:\n vlan:\n external: true\nAn added benefit of this approach is that you won't have to perform any port mapping anymore, since all ports will be exposed by default.\nImportantThis IP address won't be accessible from the Docker host due to the design of macvlan, which doesn't permit communication between the two. If this is a concern, you need to create a second macvlan as a workaround.\n\nHow can Windows acquire an IP address from my router?\nAfter configuring the container for macvlan, it is possible for Windows to become part of your home network by requesting an IP from your router, just like a real PC.\nTo enable this mode, add the following lines to your compose file:\nenvironment:\n DHCP: \"Y\"\ndevices:\n - /dev/vhost-net\ndevice_cgroup_rules:\n - 'c *:* rwm'\nNoteIn this mode, the container and Windows will each have their own separate IPs.\n\nHow do I add multiple disks?\nTo create additional disks, modify your compose file like this:\nenvironment:\n DISK2_SIZE: \"32G\"\n DISK3_SIZE: \"64G\"\nvolumes:\n - /home/example:/storage2\n - /mnt/data/example:/storage3\nHow do I pass-through a disk?\nIt is possible to pass-through disk devices directly by adding them to your compose file in this way:\ndevices:\n - /dev/sdb:/disk1\n - /dev/sdc:/disk2\nUse /disk1 if you want it to become your main drive (which will be formatted during installation), and use /disk2 and higher to add them as secondary drives (which will stay untouched).\nHow do I pass-through a USB device?\nTo pass-through a USB device, first lookup its vendor and product id via the lsusb command, then add them to your compose file like this:\nenvironment:\n ARGUMENTS: \"-device usb-host,vendorid=0x1234,productid=0x1234\"\ndevices:\n - /dev/bus/usb\nImportantIf the device is a USB disk drive, please wait until after the installation is completed before connecting it. Otherwise the installation may fail, as the order of the disks can get rearranged.\n\nHow do I verify if my system supports KVM?\nOnly Linux and Windows 11 support KVM virtualization, macOS and Windows 10 do not unfortunately.\nYou can run the following commands in Linux to check your system:\nsudo apt install cpu-checker\nsudo kvm-ok\nIf you receive an error from kvm-ok indicating that KVM cannot be used, please check whether:\n\n\nthe virtualization extensions (Intel VT-x or AMD SVM) are enabled in your BIOS.\n\n\nyou enabled \"nested virtualization\" if you are running the container inside a virtual machine.\n\n\nyou are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's.\n\n\nIf you do not receive any error from kvm-ok but the container still complains about KVM, please check whether:\n\n\nyou are not using \"Docker Desktop for Linux\" as it does not support KVM, instead make use of Docker Engine directly.\n\n\nit could help to add privileged: true to your compose file (or sudo to your docker run command), to rule out any permission issue.\n\n\nHow do I run macOS in a container?\nYou can use dockur/macos for that. It shares many of the same features, except for the automatic installation.\nIs this project legal?\nYes, this project contains only open-source code and does not distribute any copyrighted material. Any product keys found in the code are just generic placeholders provided by Microsoft for trial purposes. So under all applicable laws, this project will be considered legal.\nStars šŸŒŸ\n\nDisclaimer āš–ļø\nThe product names, logos, brands, and other trademarks referred to within this project are the property of their respective trademark holders. This project is not affiliated, sponsored, or endorsed by Microsoft Corporation.\n","length":10945,"excerpt":"Windows inside a Docker container.","siteName":null}