From 729834bdef9d495ad4479b3b328d57b2a65f00cf Mon Sep 17 00:00:00 2001 From: Eric Silver <107945446+lizoron@users.noreply.github.com> Date: Thu, 22 Aug 2024 12:14:22 -0500 Subject: [PATCH 1/4] update yarn --- yarn.lock | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/yarn.lock b/yarn.lock index 2618f345f3..e62cfc63f8 100644 --- a/yarn.lock +++ b/yarn.lock @@ -1854,10 +1854,10 @@ dependencies: "@types/mdx" "^2.0.0" -"@node-rs/jieba-darwin-x64@1.10.3": +"@node-rs/jieba-win32-x64-msvc@1.10.3": version "1.10.3" - resolved "https://registry.npmjs.org/@node-rs/jieba-darwin-x64/-/jieba-darwin-x64-1.10.3.tgz" - integrity sha512-kjxvV6G1baQo/2I3mELv5qGv4Q0rhd5srwXhypSxMWZFtSpNwCDsLcIOR5bvMBci6QVFfZOs6WD6DKiWVz0SlA== + resolved "https://registry.npmjs.org/@node-rs/jieba-win32-x64-msvc/-/jieba-win32-x64-msvc-1.10.3.tgz" + integrity sha512-j9I4+a/tf2hsLu8Sr0NhcLBVNBBQctO2mzcjemMpRa1SlEeODyic9RIyP8Ljz3YTN6MYqKh1KA9iR1xvxjxYFg== "@node-rs/jieba@^1.6.0": version "1.10.3" @@ -2073,10 +2073,10 @@ "@svgr/plugin-jsx" "8.1.0" "@svgr/plugin-svgo" "8.1.0" -"@swc/core-darwin-x64@1.7.14": +"@swc/core-win32-x64-msvc@1.7.14": version "1.7.14" - resolved "https://registry.npmjs.org/@swc/core-darwin-x64/-/core-darwin-x64-1.7.14.tgz" - integrity sha512-9iFvUnxG6FC3An5ogp5jbBfQuUmTTwy8KMB+ZddUoPB3NR1eV+Y9vOh/tfWcenSJbgOKDLgYC5D/b1mHAprsrQ== + resolved "https://registry.npmjs.org/@swc/core-win32-x64-msvc/-/core-win32-x64-msvc-1.7.14.tgz" + integrity sha512-NNrprQCK6d28mG436jVo2TD+vACHseUECacEBGZ9Ef0qfOIWS1XIt2MisQKG0Oea2VvLFl6tF/V4Lnx/H0Sn3Q== "@swc/core@^1.2.147", "@swc/core@^1.7.14": version "1.7.14" @@ -4350,11 +4350,6 @@ fs.realpath@^1.0.0: resolved "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz" integrity sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw== -fsevents@~2.3.2: - version "2.3.3" - resolved "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz" - integrity sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw== - function-bind@^1.1.2: version "1.1.2" resolved "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz" From be1b741c35593a664b58f1f505061a70eb578dc5 Mon Sep 17 00:00:00 2001 From: Eric Silver <107945446+lizoron@users.noreply.github.com> Date: Tue, 3 Sep 2024 13:55:02 -0500 Subject: [PATCH 2/4] docker es instructions --- .../create-es-from-docker.md | 167 ++++++++++++++++++ .../installation-procedure/index.md | 4 +- .../collecting-logs.md | 4 + 3 files changed, 174 insertions(+), 1 deletion(-) create mode 100644 docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md diff --git a/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md b/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md new file mode 100644 index 0000000000..3bb35518ef --- /dev/null +++ b/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md @@ -0,0 +1,167 @@ +--- +sidebar_position: 4 +--- + +# Create Execution Server On Any Linux VM Using Docker + +**Prerequisites:** + +- Docker installed on any Docker supported Linux VM: https://docs.docker.com/engine/install/ +- Quali Server 2024.1 or later + +:::important +In the docker run command, we use "--name ExecutionServer" for the container name in order to provide additional commands for gathering logs and other optional steps. +::: + +## Online Steps to Install Execution Server Using Docker + +1. Install Docker on your Linux Server machine +2. Enable Docker Ipv6 support: + 1. **Create** a file /etc/docker/daemon.json: + ```javascript + sudo touch /etc/docker/daemon.json + ``` + 2. **Edit** the file: + ```javascript + sudo nano /etc/docker/daemon.json + ``` + 3. **Add** to it (you can use any valid IPv6 CIDR): + ```javascript + { + "ipv6": true, + "fixed-cidr-v6": "2001:db8:1::/64" + } + ``` + 4. **Save** it +3. Restart the Docker Service: +```javascript +sudo systemctl restart docker +``` +4. Create an empty file named customer.config: +```javascript +touch ~/customer.config +``` +5. Run the latest version of Execution Server using Docker Hub: +```javascript +sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -e PARAMS="IP Address,Username,Password,Name for ExectionServer" -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver +``` + :::warning + Inside PARAMS="" you need to specify your Cloudshell server IP, Cloudshell Admin username, password, desirable name for the Execution Server. Example: -e PARAMS="192.168.25.4,admin,admin,ES-Docker" + ::: +:::info +- If you want to specify the version, you can edit the end of the command to include the version number. Example: qualihub/executionserver:2024.1 +- See what versions are available here: https://hub.docker.com/r/qualihub/executionserver/tags +::: + +6. Verify the new Execution Server is Online in CloudShell Portal > Manage > Execution Servers > Servers +7. **(Optional)** After the first run, if you don't want your admin password to be available as an Env +variable inside the container, you can: + 1. Verify that your customer.config file is filled with data from the first run. + ```javascript + sudo cat customer.config + ``` + 2. Stop the existing container + ```javascript + sudo docker stop ExecutionServer + ``` + 3. Delete the existing container + ```javascript + sudo docker rm ExecutionServer + ``` + 4. Run a new container with the command: + ```javascript + sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver + ``` + 5. In this case, all necessary information will be provided by the customer.config file. Be +aware that this should be the same file that you used for the first run! + +## Offline Steps to Install Execution Server Using Docker + +1. Install Docker on your Linux Server machine +2. Enable Docker Ipv6 support: + 1. **Create** a file /etc/docker/daemon.json: + ```javascript + sudo touch /etc/docker/daemon.json + ``` + 2. **Edit** the file: + ```javascript + sudo nano /etc/docker/daemon.json + ``` + 3. **Add** to it (you can use any valid ipv6 cidr): + ```javascript + { + "ipv6": true, + "fixed-cidr-v6": "2001:db8:1::/64" + } + ``` + 4. **Save** it +3. Restart the Docker Service: +```javascript +sudo systemctl restart docker +``` +4. Download **Execution Server on Docker** for your CloudShell Version from our [Download Center](https://support.quali.com/hc/en-us/articles/231613247-CloudShell-Download-Center) +5. Transfer the .tar file to your Linux Server machine +6. Load ES Docker Image: +```javascript +sudo docker load < es-2024-1.tar +``` +7. Create an empty file named customer.config: +```javascript +touch ~/customer.config +``` +8. Run a Docker Container from the image with the command: +```javascript +sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -e PARAMS="IP Address,Username,Password,Name for ExectionServer" -v ~/customer.config:/opt/ExecutionServer/customer.config quali/es-server:2024.1 +``` + :::warning + Inside PARAMS="" you need to specify your Cloudshell server IP, Cloudshell Admin username, password, desirable name for the Execution Server. Example: -e PARAMS="192.168.25.4,admin,admin,ES-Docker" + ::: + +9. Verify the new Execution Server is Online in CloudShell Portal > Manage > Execution Servers > Servers +10. **(Optional)** After the first run, if you don't want your admin password to be available as an Env +variable inside the container, you can: + 1. Verify that your customer.config file is filled with data from the first run. + ```javascript + sudo cat customer.config + ``` + 2. Stop the existing container + ```javascript + sudo docker stop ExecutionServer + ``` + 3. Delete the existing container + ```javascript + sudo docker rm ExecutionServer + ``` + 4. Run a new container with the command: + ```javascript + sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver + ``` + 5. In this case, all necessary information will be provided by the customer.config file. Be +aware that this should be the same file that you used for the first run! + +## Steps to Collect and Share Logs on Linux Using Docker + +:::note +- Since log files are located in the docker container, the commands below will copy the logs out of the container then create an archive file for each log directory +- Only step 1 and 2 are usually needed but if requested by support or R&D, please include the venv logs from step 3 +::: + +1. Create an archive file from `/opt/ExecutionServer/Logs/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-Logs && sudo docker exec ExecutionServer find /opt/ExecutionServer/Logs/ -mindepth 1 -maxdepth 1 -type d -name "*" -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-Logs && tar -czvf ${current_date}-Logs.tar.gz ${current_date}-Logs && sudo rm -rf ~/${current_date}-Logs +``` + +2. Create an archive file from `/var/log/qualisystems/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-qualisystems && sudo docker exec ExecutionServer find /var/log/qualisystems/ -mindepth 1 -maxdepth 1 -type d -name "*" -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-qualisystems && tar -czvf ${current_date}-qualisystems.tar.gz ${current_date}-qualisystems && sudo rm -rf ~/${current_date}-qualisystems +``` + +3. **(Optional, only needed if specifically requested for Shell issues)** Create an archive file from `/usr/share/QualiSystems/venv/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-venv && sudo docker exec ExecutionServer find /usr/share/QualiSystems/venv/ -mindepth 1 -maxdepth 1 -type d -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-venv && tar -czvf ${current_date}-venv.tar.gz ${current_date}-venv && sudo rm -rf ~/${current_date}-venv +``` + +4. Transfer your newly created archived files named *-Logs, *-qualisystems, and *-venv from your home directory and share them to whom it may concern +:::note +If you're using a Windows machine to extract logs from the Linux execution server, we recommend using an SCP client to connect via SSH to the Linux execution server to browse though the logs. You can also transfer the files to a Windows machine in order to send them, if needed. +::: diff --git a/docs/install-configure/linux-virtual-appliance/installation-procedure/index.md b/docs/install-configure/linux-virtual-appliance/installation-procedure/index.md index 33461fbba5..955b710e5f 100644 --- a/docs/install-configure/linux-virtual-appliance/installation-procedure/index.md +++ b/docs/install-configure/linux-virtual-appliance/installation-procedure/index.md @@ -8,6 +8,8 @@ This chapter explains how to install **CloudShell Execution Server Linux Virtual - For VMware vSphere users: [Create VM using the OVF Template (vSphere)](./create-es-from-ovf.md) - For Linux KVM users: [Create VM using the qcow2 Image File (KVM)](./create-es-from-qcow2.md) - - If you already have an available VM: [Create the Linux Execution Server from a Script](./create-es-from-script.md) + - If you already have an available Linux VM: + - [Create the Linux Execution Server from a Script](./create-es-from-script.md) + - [Create Execution Server On Any Linux VM Using Docker](./create-es-from-docker.md)(CloudShell 2024.1 and above) 2. Perform the post installation procedures described here: [Post Installation](../../install-configure/linux-virtual-appliance/post-installation). \ No newline at end of file diff --git a/docs/troubleshooting/troubleshooting-overview/collecting-logs.md b/docs/troubleshooting/troubleshooting-overview/collecting-logs.md index aad415729e..e11443d508 100644 --- a/docs/troubleshooting/troubleshooting-overview/collecting-logs.md +++ b/docs/troubleshooting/troubleshooting-overview/collecting-logs.md @@ -217,6 +217,10 @@ If you are using a Windows machine to extract logs from the Linux execution serv - `./opt/ExecutionServer/Logs` - `/var/log/qualiSystems/` +## Linux execution server logs (Docker) + +If you set up an Execution Server using Docker, see [Steps to Collect and Share Logs on Linux Using Docker](../../install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md#steps-to-collect-and-share-logs-on-linux-using-docker). + ## Windows execution server logs When a Windows-based execution server runs a Python command, either shell-based or an orchestration script, the execution server's logs will be saved here: `C:\ProgramData\QualiSystems\logs`. From ddc94ef8659691616f2db0b2eba4fdaa67a4f294 Mon Sep 17 00:00:00 2001 From: Eric Silver <107945446+lizoron@users.noreply.github.com> Date: Tue, 3 Sep 2024 14:00:54 -0500 Subject: [PATCH 3/4] fixed wordlist --- .wordlist.txt | 4 +++- .../installation-procedure/create-es-from-docker.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.wordlist.txt b/.wordlist.txt index dcac3bf44a..74c0697c57 100644 --- a/.wordlist.txt +++ b/.wordlist.txt @@ -1623,4 +1623,6 @@ GetExecutionServers GetResourceAttributeValues GetResourceDetails GetResourcesAttributeValues -performant \ No newline at end of file +performant +executionserver +ipv \ No newline at end of file diff --git a/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md b/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md index 3bb35518ef..1d73922b89 100644 --- a/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md +++ b/docs/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md @@ -16,7 +16,7 @@ In the docker run command, we use "--name ExecutionServer" for the container nam ## Online Steps to Install Execution Server Using Docker 1. Install Docker on your Linux Server machine -2. Enable Docker Ipv6 support: +2. Enable Docker IPv6 support: 1. **Create** a file /etc/docker/daemon.json: ```javascript sudo touch /etc/docker/daemon.json From 475457a11dcf554da7386328e43979e548705673 Mon Sep 17 00:00:00 2001 From: Eric Silver <107945446+lizoron@users.noreply.github.com> Date: Tue, 3 Sep 2024 14:35:48 -0500 Subject: [PATCH 4/4] added instruction and other changes to version 2024.1 docs --- .../create-es-from-docker.md | 167 ++++++++++++++++++ .../installation-procedure/index.md | 4 +- .../collecting-logs.md | 4 + 3 files changed, 174 insertions(+), 1 deletion(-) create mode 100644 versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md diff --git a/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md b/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md new file mode 100644 index 0000000000..1d73922b89 --- /dev/null +++ b/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md @@ -0,0 +1,167 @@ +--- +sidebar_position: 4 +--- + +# Create Execution Server On Any Linux VM Using Docker + +**Prerequisites:** + +- Docker installed on any Docker supported Linux VM: https://docs.docker.com/engine/install/ +- Quali Server 2024.1 or later + +:::important +In the docker run command, we use "--name ExecutionServer" for the container name in order to provide additional commands for gathering logs and other optional steps. +::: + +## Online Steps to Install Execution Server Using Docker + +1. Install Docker on your Linux Server machine +2. Enable Docker IPv6 support: + 1. **Create** a file /etc/docker/daemon.json: + ```javascript + sudo touch /etc/docker/daemon.json + ``` + 2. **Edit** the file: + ```javascript + sudo nano /etc/docker/daemon.json + ``` + 3. **Add** to it (you can use any valid IPv6 CIDR): + ```javascript + { + "ipv6": true, + "fixed-cidr-v6": "2001:db8:1::/64" + } + ``` + 4. **Save** it +3. Restart the Docker Service: +```javascript +sudo systemctl restart docker +``` +4. Create an empty file named customer.config: +```javascript +touch ~/customer.config +``` +5. Run the latest version of Execution Server using Docker Hub: +```javascript +sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -e PARAMS="IP Address,Username,Password,Name for ExectionServer" -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver +``` + :::warning + Inside PARAMS="" you need to specify your Cloudshell server IP, Cloudshell Admin username, password, desirable name for the Execution Server. Example: -e PARAMS="192.168.25.4,admin,admin,ES-Docker" + ::: +:::info +- If you want to specify the version, you can edit the end of the command to include the version number. Example: qualihub/executionserver:2024.1 +- See what versions are available here: https://hub.docker.com/r/qualihub/executionserver/tags +::: + +6. Verify the new Execution Server is Online in CloudShell Portal > Manage > Execution Servers > Servers +7. **(Optional)** After the first run, if you don't want your admin password to be available as an Env +variable inside the container, you can: + 1. Verify that your customer.config file is filled with data from the first run. + ```javascript + sudo cat customer.config + ``` + 2. Stop the existing container + ```javascript + sudo docker stop ExecutionServer + ``` + 3. Delete the existing container + ```javascript + sudo docker rm ExecutionServer + ``` + 4. Run a new container with the command: + ```javascript + sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver + ``` + 5. In this case, all necessary information will be provided by the customer.config file. Be +aware that this should be the same file that you used for the first run! + +## Offline Steps to Install Execution Server Using Docker + +1. Install Docker on your Linux Server machine +2. Enable Docker Ipv6 support: + 1. **Create** a file /etc/docker/daemon.json: + ```javascript + sudo touch /etc/docker/daemon.json + ``` + 2. **Edit** the file: + ```javascript + sudo nano /etc/docker/daemon.json + ``` + 3. **Add** to it (you can use any valid ipv6 cidr): + ```javascript + { + "ipv6": true, + "fixed-cidr-v6": "2001:db8:1::/64" + } + ``` + 4. **Save** it +3. Restart the Docker Service: +```javascript +sudo systemctl restart docker +``` +4. Download **Execution Server on Docker** for your CloudShell Version from our [Download Center](https://support.quali.com/hc/en-us/articles/231613247-CloudShell-Download-Center) +5. Transfer the .tar file to your Linux Server machine +6. Load ES Docker Image: +```javascript +sudo docker load < es-2024-1.tar +``` +7. Create an empty file named customer.config: +```javascript +touch ~/customer.config +``` +8. Run a Docker Container from the image with the command: +```javascript +sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -e PARAMS="IP Address,Username,Password,Name for ExectionServer" -v ~/customer.config:/opt/ExecutionServer/customer.config quali/es-server:2024.1 +``` + :::warning + Inside PARAMS="" you need to specify your Cloudshell server IP, Cloudshell Admin username, password, desirable name for the Execution Server. Example: -e PARAMS="192.168.25.4,admin,admin,ES-Docker" + ::: + +9. Verify the new Execution Server is Online in CloudShell Portal > Manage > Execution Servers > Servers +10. **(Optional)** After the first run, if you don't want your admin password to be available as an Env +variable inside the container, you can: + 1. Verify that your customer.config file is filled with data from the first run. + ```javascript + sudo cat customer.config + ``` + 2. Stop the existing container + ```javascript + sudo docker stop ExecutionServer + ``` + 3. Delete the existing container + ```javascript + sudo docker rm ExecutionServer + ``` + 4. Run a new container with the command: + ```javascript + sudo docker run -d --name ExecutionServer --restart unless-stopped -p 5093:5093 -v ~/customer.config:/opt/ExecutionServer/customer.config qualihub/executionserver + ``` + 5. In this case, all necessary information will be provided by the customer.config file. Be +aware that this should be the same file that you used for the first run! + +## Steps to Collect and Share Logs on Linux Using Docker + +:::note +- Since log files are located in the docker container, the commands below will copy the logs out of the container then create an archive file for each log directory +- Only step 1 and 2 are usually needed but if requested by support or R&D, please include the venv logs from step 3 +::: + +1. Create an archive file from `/opt/ExecutionServer/Logs/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-Logs && sudo docker exec ExecutionServer find /opt/ExecutionServer/Logs/ -mindepth 1 -maxdepth 1 -type d -name "*" -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-Logs && tar -czvf ${current_date}-Logs.tar.gz ${current_date}-Logs && sudo rm -rf ~/${current_date}-Logs +``` + +2. Create an archive file from `/var/log/qualisystems/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-qualisystems && sudo docker exec ExecutionServer find /var/log/qualisystems/ -mindepth 1 -maxdepth 1 -type d -name "*" -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-qualisystems && tar -czvf ${current_date}-qualisystems.tar.gz ${current_date}-qualisystems && sudo rm -rf ~/${current_date}-qualisystems +``` + +3. **(Optional, only needed if specifically requested for Shell issues)** Create an archive file from `/usr/share/QualiSystems/venv/` with the command below: +```javascript +current_date=$(date +%Y-%m-%d) && mkdir ~/${current_date}-venv && sudo docker exec ExecutionServer find /usr/share/QualiSystems/venv/ -mindepth 1 -maxdepth 1 -type d -mtime -7 -print0 | sudo xargs -0 -I {} docker cp ExecutionServer:{} ~/${current_date}-venv && tar -czvf ${current_date}-venv.tar.gz ${current_date}-venv && sudo rm -rf ~/${current_date}-venv +``` + +4. Transfer your newly created archived files named *-Logs, *-qualisystems, and *-venv from your home directory and share them to whom it may concern +:::note +If you're using a Windows machine to extract logs from the Linux execution server, we recommend using an SCP client to connect via SSH to the Linux execution server to browse though the logs. You can also transfer the files to a Windows machine in order to send them, if needed. +::: diff --git a/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/index.md b/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/index.md index 33461fbba5..955b710e5f 100644 --- a/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/index.md +++ b/versioned_docs/version-2024.1/install-configure/linux-virtual-appliance/installation-procedure/index.md @@ -8,6 +8,8 @@ This chapter explains how to install **CloudShell Execution Server Linux Virtual - For VMware vSphere users: [Create VM using the OVF Template (vSphere)](./create-es-from-ovf.md) - For Linux KVM users: [Create VM using the qcow2 Image File (KVM)](./create-es-from-qcow2.md) - - If you already have an available VM: [Create the Linux Execution Server from a Script](./create-es-from-script.md) + - If you already have an available Linux VM: + - [Create the Linux Execution Server from a Script](./create-es-from-script.md) + - [Create Execution Server On Any Linux VM Using Docker](./create-es-from-docker.md)(CloudShell 2024.1 and above) 2. Perform the post installation procedures described here: [Post Installation](../../install-configure/linux-virtual-appliance/post-installation). \ No newline at end of file diff --git a/versioned_docs/version-2024.1/troubleshooting/troubleshooting-overview/collecting-logs.md b/versioned_docs/version-2024.1/troubleshooting/troubleshooting-overview/collecting-logs.md index aad415729e..e11443d508 100644 --- a/versioned_docs/version-2024.1/troubleshooting/troubleshooting-overview/collecting-logs.md +++ b/versioned_docs/version-2024.1/troubleshooting/troubleshooting-overview/collecting-logs.md @@ -217,6 +217,10 @@ If you are using a Windows machine to extract logs from the Linux execution serv - `./opt/ExecutionServer/Logs` - `/var/log/qualiSystems/` +## Linux execution server logs (Docker) + +If you set up an Execution Server using Docker, see [Steps to Collect and Share Logs on Linux Using Docker](../../install-configure/linux-virtual-appliance/installation-procedure/create-es-from-docker.md#steps-to-collect-and-share-logs-on-linux-using-docker). + ## Windows execution server logs When a Windows-based execution server runs a Python command, either shell-based or an orchestration script, the execution server's logs will be saved here: `C:\ProgramData\QualiSystems\logs`.