Research if Linux deployment script can be deployed with WSL #1002

Closed
opened 2026-05-19 08:08:20 +00:00 by b24johka · 4 comments
Collaborator

This could potentially fix the #948 and #915

This could potentially fix the https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/948 and https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/915
Author
Collaborator

Research:

It is very easy to run Linux scripts with WSL, and it is actually a common standard for docker projects for CI/CD purposes. For example, some projects only use Linux scripts and run them with WSL. That way you could rely on only Linux scripts.

Since docker desktop (Windows) is already running on WSL with the VM (docker-desktop), the dependency is already included in the project. All we need to do is to create another OS preferebly Debian (for compatibility reasons with docker) and run the DeployTrigger.sh.

The question is rather, in what scale should we utilize WSL with Debian for our gain?
Should it only be installed during deployment (And uninstalled right after?), or is there a reason to install it in the installation script and use it for more things.

# Research: It is very easy to run Linux scripts with WSL, and it is actually a common standard for docker projects for CI/CD purposes. For example, some projects only use Linux scripts and run them with WSL. That way you could rely on only Linux scripts. Since docker desktop (Windows) is already running on WSL with the VM (docker-desktop), the dependency is already included in the project. All we need to do is to create another OS preferebly Debian (for compatibility reasons with docker) and run the **DeployTrigger.sh**. The question is rather, in what scale should we utilize WSL with Debian for our gain? Should it only be installed during deployment (And uninstalled right after?), or is there a reason to install it in the installation script and use it for more things.
Author
Collaborator

After discussion with peers we believe the right option is to install it during deployment and keep it installed, since it would be a little unnecessary to keep installing it each deploy.

After discussion with peers we believe the right option is to install it during deployment and keep it installed, since it would be a little unnecessary to keep installing it each deploy.
Author
Collaborator

Initially it looked as if this solution would work fine, this was until it was discovered that the VM will not be able to run a SSH to a remote server because of NAT settings and WSL constraints to establishing an SSH connection. The research suggests that it is possible but would need alot more additional work, uncertain if its worth the effort to be able to deploy from Windows machine.

Initially it looked as if this solution would work fine, this was until it was discovered that the VM will not be able to run a SSH to a remote server because of NAT settings and WSL constraints to establishing an SSH connection. The research suggests that it is possible but would need alot more additional work, uncertain if its worth the effort to be able to deploy from Windows machine.
Author
Collaborator

After the problems with WSL it was decided to take a second look at the WIP PR for windows deployment script which spawned this issue, the problems were identified and solved. I think this issue can be closed without a review because its not relevant.

After the problems with WSL it was decided to take a second look at the WIP PR for windows deployment script which spawned this issue, the problems were identified and solved. I think this issue can be closed without a review because its not relevant.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#1002
No description provided.