Zengtudor/windows_in_docker
1
0
Fork 0
mirror of https://github.com/dockur/windows.git synced 2025-12-16 20:23:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

chore: remove compose files

Browse Source
This commit is contained in:
synacktra.work@gmail.com 2025-11-26 13:50:52 +05:30
parent e241426eea
commit 73c8661390
3 changed files with 130 additions and 137 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
compose.prepare.yml
View File

@ -1,19 +0,0 @@
services:
prepare-windows:
image: windows-local:latest
container_name: prepare-windows
environment:
ISO_FILE: "${ISO_FILE:?Error: required env var not set}"
STORAGE_DIR: "${STORAGE_DIR:?Error: required env var not set}"
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
volumes:
- ${ISO_FILE}:/custom.iso
- ${STORAGE_DIR}:/storage

17
compose.yml
View File

@ -1,17 +0,0 @@
services:
windows:
image: windows-local:latest
container_name: windows
environment:
STORAGE_DIR: "${STORAGE_DIR:?Error: required env var not set}"
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
volumes:
- ${STORAGE_DIR}:/storage

229
readme.md
View File

@ -10,33 +10,86 @@ Local Windows inside a Docker container.
## Usage 🐳 ## Usage 🐳
### Via Docker Compose: ### Building the Image
> See [compose.yml](compose.yml) for the complete configuration.
To prepare a golden image from a custom ISO:
```bash ```bash
STORAGE_DIR=/path/to/storage ISO_FILE=/path/to/custom.iso \ docker build -t windows-local:latest .
docker compose -f compose.prepare.yml up
``` ```
Start the container (using the golden image): ### Preparing Golden Image (First Time)
```bash
STORAGE_DIR=/path/to/storage docker compose up
```
### Via Docker CLI: Mount your Windows ISO and let it install automatically:
```bash ```bash
docker run -it --rm \ docker run -it --rm \
-p 8006:8006 \ --name prepare-windows \
--device=/dev/kvm \ --device=/dev/kvm \
--cap-add NET_ADMIN \ --cap-add NET_ADMIN \
--mount type=bind,source=./custom.iso,target=/custom.iso \ --mount type=bind,source=/path/to/windows.iso,target=/custom.iso \
-v /path/to/storage:/storage \
-p 8006:8006 \
-e RAM_SIZE=4G \
-e CPU_CORES=2 \
-e DISK_SIZE=64G \
--stop-timeout 120 \ --stop-timeout 120 \
windows-local:latest windows-local:latest
``` ```
The container will automatically:
- Install Windows with automated configuration
- Create a golden image in `/storage`
- Exit when preparation is complete
### Running from Golden Image
After preparation, start Windows from the saved golden image:
```bash
docker run -it --rm \
--name windows \
--device=/dev/kvm \
--cap-add NET_ADMIN \
-v /path/to/storage:/storage \
-p 8006:8006 \
-p 3389:3389 \
-e RAM_SIZE=8G \
-e CPU_CORES=4 \
--stop-timeout 120 \
windows-local:latest
```
Access the desktop via browser at http://localhost:8006
### Custom Installation with OEM Scripts
You can provide custom installation scripts that run after installation:
```bash
docker run -it --rm \
--name prepare-windows \
--device=/dev/kvm \
--cap-add NET_ADMIN \
--mount type=bind,source=/path/to/windows.iso,target=/custom.iso \
--mount type=bind,source=/path/to/oem,target=/oem \
-v /path/to/storage:/storage \
-p 8006:8006 \
--stop-timeout 120 \
windows-local:latest
```
Create an `/oem/install.bat` script that will execute after installation:
```batch
@echo off
REM Example OEM installation script
REM Install additional software
echo Installing additional packages...
REM Configure system
echo Custom setup complete!
```
## Compatibility ⚙️ ## Compatibility ⚙️
| **Product** | **Platform** | | | **Product** | **Platform** | |
@ -69,23 +122,21 @@ docker run -it --rm \
### How do I select the Windows language? ### How do I select the Windows language?
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: By default, the English version of Windows will be downloaded. But you can specify an alternative language using the `LANGUAGE` environment variable:
```yaml ```bash
environment: -e LANGUAGE="French"
LANGUAGE: "French"
``` ```
You can choose between: 🇦🇪 Arabic, 🇧🇬 Bulgarian, 🇨🇳 Chinese, 🇭🇷 Croatian, 🇨🇿 Czech, 🇩🇰 Danish, 🇳🇱 Dutch, 🇬🇧 English, 🇪🇪 Estionian, 🇫🇮 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. You can choose between: 🇦🇪 Arabic, 🇧🇬 Bulgarian, 🇨🇳 Chinese, 🇭🇷 Croatian, 🇨🇿 Czech, 🇩🇰 Danish, 🇳🇱 Dutch, 🇬🇧 English, 🇪🇪 Estionian, 🇫🇮 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.
### How do I select the keyboard layout? ### How do I select the keyboard layout?
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: If you want to use a keyboard layout or locale that is not the default for your selected language, you can specify the `KEYBOARD` and `REGION` variables with a culture code:
```yaml ```bash
environment: -e REGION="en-US" \
REGION: "en-US" -e KEYBOARD="en-US"
KEYBOARD: "en-US"
``` ```
> [!NOTE] > [!NOTE]
@ -93,22 +144,18 @@ docker run -it --rm \
### How do I change the storage location? ### How do I change the storage location?
To change the storage location, include the following bind mount in your compose file: To change the storage location, modify the volume mount:
```yaml ```bash
volumes: -v /custom/storage/path:/storage
- ./windows:/storage
``` ```
Replace the example path `./windows` with the desired storage folder.
### How do I change the size of the disk? ### How do I change the size of the disk?
To expand the default size of 64 GB, add the `DISK_SIZE` setting to your compose file and set it to your preferred capacity: To expand the default size of 64 GB, set the `DISK_SIZE` environment variable:
```yaml ```bash
environment: -e DISK_SIZE="256G"
DISK_SIZE: "256G"
``` ```
> [!TIP] > [!TIP]
@ -116,11 +163,10 @@ docker run -it --rm \
### How do I share files with the host? ### How do I share files with the host?
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: 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:
```yaml ```bash
volumes: -v /home/user/example:/data
- /home/user/example:/data
``` ```
The example folder `/home/user/example` will be available as ` \\host.lan\Data`. The example folder `/home/user/example` will be available as ` \\host.lan\Data`.
@ -130,58 +176,55 @@ docker run -it --rm \
### How do I run a script after installation? ### How do I run a script after installation?
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: 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:
```yaml ```bash
volumes: --mount type=bind,source=/home/user/example,target=/oem
- /home/user/example:/oem
``` ```
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. 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.
See the [Custom Installation with OEM Scripts](#custom-installation-with-oem-scripts) section above for a complete example.
### How do I change the amount of CPU or RAM? ### How do I change the amount of CPU or RAM?
By default, the container will be allowed to use a maximum of 2 CPU cores and 4 GB of RAM. By default, the container will be allowed to use a maximum of 2 CPU cores and 4 GB of RAM.
If you want to adjust this, you can specify the desired amount using the following environment variables: If you want to adjust this, specify the desired amount:
```yaml ```bash
environment: -e RAM_SIZE="8G" \
RAM_SIZE: "8G" -e CPU_CORES="4"
CPU_CORES: "4"
``` ```
### How do I configure the username and password? ### How do I configure the username and password?
By default, a user called `Docker` is created during the installation, with an empty password. By default, a user called `Docker` is created during the installation, with an empty password.
If you want to use different credentials, you can change them in your compose file: If you want to use different credentials, specify them:
```yaml ```bash
environment: -e USERNAME="bill" \
USERNAME: "bill" -e PASSWORD="gates"
PASSWORD: "gates"
``` ```
### How do I select the Windows language? ### How do I select the Windows language?
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: By default, the English version of Windows will be downloaded. But you can specify an alternative language using the `LANGUAGE` environment variable:
```yaml ```bash
environment: -e LANGUAGE="French"
LANGUAGE: "French"
``` ```
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. 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.
### How do I select the keyboard layout? ### How do I select the keyboard layout?
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: If you want to use a keyboard layout or locale that is not the default for your selected language, you can specify the `KEYBOARD` and `REGION` variables with a culture code:
```yaml ```bash
environment: -e REGION="en-US" \
REGION: "en-US" -e KEYBOARD="en-US"
KEYBOARD: "en-US"
``` ```
> [!NOTE] > [!NOTE]
@ -210,20 +253,14 @@ docker run -it --rm \
Be sure to modify these values to match your local subnet. Be sure to modify these values to match your local subnet.
Once you have created the network, change your compose file to look as follows: Once you have created the network, add the network configuration to your run command:
```yaml ```bash
services: docker run -it --rm \
windows: --name windows \
container_name: windows --network vlan \
..<snip>.. --ip 192.168.0.100 \
networks: ...
vlan:
ipv4_address: 192.168.0.100
networks:
vlan:
external: true
``` ```
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. 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.
@ -235,15 +272,12 @@ docker run -it --rm \
After configuring the container for [macvlan](#how-do-i-assign-an-individual-ip-address-to-the-container), it is possible for Windows to become part of your home network by requesting an IP from your router, just like a real PC. After configuring the container for [macvlan](#how-do-i-assign-an-individual-ip-address-to-the-container), it is possible for Windows to become part of your home network by requesting an IP from your router, just like a real PC.
To enable this mode, add the following lines to your compose file: To enable this mode, add the following to your run command:
```yaml ```bash
environment: -e DHCP="Y" \
DHCP: "Y" --device=/dev/vhost-net \
devices: --device-cgroup-rule='c *:* rwm'
- /dev/vhost-net
device_cgroup_rules:
- 'c *:* rwm'
``` ```
> [!NOTE] > [!NOTE]
@ -251,38 +285,33 @@ docker run -it --rm \
### How do I add multiple disks? ### How do I add multiple disks?
To create additional disks, modify your compose file like this: To create additional disks, add the following to your run command:
```yaml ```bash
environment: -e DISK2_SIZE="32G" \
DISK2_SIZE: "32G" -e DISK3_SIZE="64G" \
DISK3_SIZE: "64G" -v /home/example:/storage2 \
volumes: -v /mnt/data/example:/storage3
- /home/example:/storage2
- /mnt/data/example:/storage3
``` ```
### How do I pass-through a disk? ### How do I pass-through a disk?
It is possible to pass-through disk devices directly by adding them to your compose file in this way: It is possible to pass-through disk devices directly:
```yaml ```bash
devices: --device=/dev/sdb:/disk1 \
- /dev/sdb:/disk1 --device=/dev/sdc:/disk2
- /dev/sdc:/disk2
``` ```
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). 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).
### How do I pass-through a USB device? ### How do I pass-through a USB device?
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: To pass-through a USB device, first lookup its vendor and product id via the `lsusb` command, then add them to your run command:
```yaml ```bash
environment: -e ARGUMENTS="-device usb-host,vendorid=0x1234,productid=0x1234" \
ARGUMENTS: "-device usb-host,vendorid=0x1234,productid=0x1234" --device=/dev/bus/usb
devices:
- /dev/bus/usb
``` ```
> [!IMPORTANT] > [!IMPORTANT]
@ -307,5 +336,5 @@ docker run -it --rm \
- you are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's. - you are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's.
If you didn't receive any error from `kvm-ok` at all, but the container still complains that `/dev/kvm` is missing, it might help to add `privileged: true` to your compose file (or `--privileged` to your `run` command), to rule out any permission issue. If you didn't receive any error from `kvm-ok` at all, but the container still complains that `/dev/kvm` is missing, try adding `--privileged` to your `run` command to rule out any permission issue.