Skip to content
Snippets Groups Projects
Commit 9c0c3984 authored by starbr3aker's avatar starbr3aker
Browse files

Resolved comments

parent 0826a238
No related branches found
No related tags found
No related merge requests found
...@@ -436,7 +436,7 @@ FREERDP_COMMAND="" ...@@ -436,7 +436,7 @@ FREERDP_COMMAND=""
> [!NOTE] > [!NOTE]
> If you encounter issues with tls certificate getting rejected, delete the existing `.pem` file with > If you encounter issues with tls certificate getting rejected, delete the existing `.pem` file with
> `rm -rf .config/freerdp/server/127.0.0.1_3389.pem` and run > `rm ~/.config/freerdp/server/127.0.0.1_3389.pem` and run
> `xfreerdp3 /u:MyWindowsUser /p:MyWindowsPassword /v:127.0.0.1 /cert:tofu` > `xfreerdp3 /u:MyWindowsUser /p:MyWindowsPassword /v:127.0.0.1 /cert:tofu`
> to set up Trust On First Authentication. Then retry the `setup.sh` script. > to set up Trust On First Authentication. Then retry the `setup.sh` script.
......
...@@ -37,5 +37,5 @@ services: ...@@ -37,5 +37,5 @@ services:
#- /path/to/windows/install/media.iso:/custom.iso # Uncomment to use a custom Windows ISO. If specified, 'VERSION' (e.g. 'tiny11') will be ignored. #- /path/to/windows/install/media.iso:/custom.iso # Uncomment to use a custom Windows ISO. If specified, 'VERSION' (e.g. 'tiny11') will be ignored.
devices: devices:
- /dev/kvm # Enable KVM. - /dev/kvm # Enable KVM.
#- /dev/sdX:/disk1 # Uncomment to mount a disk directly within the Windows VM (Note: 'disk1' will be mounted as the main drive. THIS DISK WILL BE FORMATTED DURING COMPOSE). #- /dev/sdX:/disk1 # Uncomment to mount a disk directly within the Windows VM (Note: 'disk1' will be mounted as the main drive. THIS DISK WILL BE FORMATTED BY DOCKER).
#- /dev/sdY:/disk2 # Uncomment to mount a disk directly within the Windows VM (Note: 'disk2' and higher will be mounted as secondary drives THIS DISK WILL NOT BE FORMATTED). #- /dev/sdY:/disk2 # Uncomment to mount a disk directly within the Windows VM (Note: 'disk2' and higher will be mounted as secondary drives THIS DISK WILL NOT BE FORMATTED).
...@@ -7,7 +7,7 @@ Although WinApps supports using `QEMU+KVM+libvirt` as a backend for running Wind ...@@ -7,7 +7,7 @@ Although WinApps supports using `QEMU+KVM+libvirt` as a backend for running Wind
> [!IMPORTANT] > [!IMPORTANT]
> WinApps does __NOT__ officially support versions of Windows prior to Windows 10. Despite this, it may be possible to achieve a successful installation with some additional experimentation. If you find a way to achieve this, please share your solution through a pull request for the benefit of other users. > WinApps does __NOT__ officially support versions of Windows prior to Windows 10. Despite this, it may be possible to achieve a successful installation with some additional experimentation. If you find a way to achieve this, please share your solution through a pull request for the benefit of other users.
> Possible setup instructions for Windows 10: > Possible setup instructions for Windows 10:
> - 'Professional', 'Enterprise' or 'Server' editions of Windows are required to run RDP applications. Windows 'Home' will NOT suffice. It is recommended to download the ISO from a reputed source, as the built in downloader from dockur (default set to `tiny11`) will take longer than it would to download from a browser/torrent. > - 'Professional', 'Enterprise' or 'Server' editions of Windows are required to run RDP applications. Windows 'Home' will __NOT__ suffice. It is recommended to download the ISO from a reputed source, as the built in downloader from dockur (default set to `tiny11`) will take longer than it would to download from a browser/torrent.
> - It is recommended to edit the initial `compose.yaml` file to keep your required username and password from the beginning. > - It is recommended to edit the initial `compose.yaml` file to keep your required username and password from the beginning.
> - It is recommended to not use `sudo` to force commands to run. Add your user to the relevant permissions group wherever possible. > - It is recommended to not use `sudo` to force commands to run. Add your user to the relevant permissions group wherever possible.
...@@ -32,12 +32,7 @@ Please refer to the [original GitHub repository](https://github.com/dockur/windo ...@@ -32,12 +32,7 @@ Please refer to the [original GitHub repository](https://github.com/dockur/windo
> [!NOTE] > [!NOTE]
> If you want to undo all your changes and start from scratch, run the following. For `podman`, replace `docker` with `podman`. > If you want to undo all your changes and start from scratch, run the following. For `podman`, replace `docker` with `podman`.
> ```bash > ```bash
> docker ps # verify if you have any dockers created > docker compose down --rmi=all --volumes
> docker rm -v -f $(docker ps -qa) # will remove all running dockers (EXERCISE CAUTION)
> docker container ls # see if you have any containers running
> docker container rm containerName # to remove any old containers
> docker volume ls # for old volumes. Docker will reuse old volumes which may have previous installations of windows
> docker volume rm volumeName
> ``` > ```
### Installing Windows ### Installing Windows
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment