mirror of
				https://github.com/dockur/windows.git
				synced 2025-11-03 22:04:29 +00:00 
			
		
		
		
	docs: Readme (#1108)
This commit is contained in:
		
							parent
							
								
									64ddb6d774
								
							
						
					
					
						commit
						b465f78646
					
				
							
								
								
									
										83
									
								
								readme.md
									
									
									
									
									
								
							
							
						
						
									
										83
									
								
								readme.md
									
									
									
									
									
								
							@ -162,48 +162,6 @@ kubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/mas
 | 
			
		||||
> [!TIP]
 | 
			
		||||
> You can map this path to a drive letter in Windows, for easier access.
 | 
			
		||||
 | 
			
		||||
### How do I install a custom image?
 | 
			
		||||
 | 
			
		||||
  In order to download an unsupported ISO image, specify its URL in the `VERSION` environment variable:
 | 
			
		||||
  
 | 
			
		||||
  ```yaml
 | 
			
		||||
  environment:
 | 
			
		||||
    VERSION: "https://example.com/win.iso"
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  Alternatively, you can also skip the download and use a local file instead, by binding it in your compose file in this way:
 | 
			
		||||
  
 | 
			
		||||
  ```yaml
 | 
			
		||||
  volumes:
 | 
			
		||||
    - ./example.iso:/custom.iso
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  Replace the example path `./example.iso` with the filename of your desired ISO file. The value of `VERSION` will be ignored in this case.
 | 
			
		||||
 | 
			
		||||
### 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:
 | 
			
		||||
 | 
			
		||||
  ```yaml
 | 
			
		||||
  volumes:
 | 
			
		||||
    -  ./example:/oem
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  The example folder `./example` will be copied to `C:\OEM` and the containing `install.bat` will be executed during the last step of the automatic installation.
 | 
			
		||||
 | 
			
		||||
### How do I perform a manual installation?
 | 
			
		||||
 | 
			
		||||
  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.
 | 
			
		||||
 | 
			
		||||
  However, if you insist on performing the installation manually, add the following environment variable to your compose file:
 | 
			
		||||
 | 
			
		||||
  ```yaml
 | 
			
		||||
  environment:
 | 
			
		||||
    MANUAL: "Y"
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
### 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.
 | 
			
		||||
@ -250,6 +208,47 @@ kubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/mas
 | 
			
		||||
    REGION: "en-US"
 | 
			
		||||
    KEYBOARD: "en-US"
 | 
			
		||||
  ```
 | 
			
		||||
### How do I install a custom image?
 | 
			
		||||
 | 
			
		||||
  In order to download an unsupported ISO image, specify its URL in the `VERSION` environment variable:
 | 
			
		||||
  
 | 
			
		||||
  ```yaml
 | 
			
		||||
  environment:
 | 
			
		||||
    VERSION: "https://example.com/win.iso"
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  Alternatively, you can also skip the download and use a local file instead, by binding it in your compose file in this way:
 | 
			
		||||
  
 | 
			
		||||
  ```yaml
 | 
			
		||||
  volumes:
 | 
			
		||||
    - ./example.iso:/custom.iso
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  Replace the example path `./example.iso` with the filename of your desired ISO file. The value of `VERSION` will be ignored in this case.
 | 
			
		||||
 | 
			
		||||
### 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:
 | 
			
		||||
 | 
			
		||||
  ```yaml
 | 
			
		||||
  volumes:
 | 
			
		||||
    -  ./example:/oem
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
  The example folder `./example` will be copied to `C:\OEM` and the containing `install.bat` will be executed during the last step of the automatic installation.
 | 
			
		||||
 | 
			
		||||
### How do I perform a manual installation?
 | 
			
		||||
 | 
			
		||||
  It's recommended to stick to the automatic installation, as it adjusts various settings to prevent common issues when running Windows inside a virtual environment.
 | 
			
		||||
 | 
			
		||||
  However, if you insist on performing the installation manually on your own risk, add the following environment variable to your compose file:
 | 
			
		||||
 | 
			
		||||
  ```yaml
 | 
			
		||||
  environment:
 | 
			
		||||
    MANUAL: "Y"
 | 
			
		||||
  ```
 | 
			
		||||
 | 
			
		||||
### How do I connect using RDP?
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
		Loading…
	
		Reference in New Issue
	
	Block a user