TorizonCore Builder in Windows 10 PowerShell

Our company has some WSL limits on Windows 10. I wonder if it is possible to use torizoncore builder in Windows PowerShell ?


Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Hello DN,

I understand you’re inquiring about the possibility of using TorizonCore Builder directly in Windows PowerShell due to WSL limitations in your environment. Unfortunately, TorizonCore Builder is designed to run in a Linux environment or a Linux-like environment such as WSL 2 because it relies on a Linux-based filesystem and Docker. It cannot be executed directly in Windows PowerShell without the WSL 2 layer. The requirement for WSL 2 is due to the need for a compatible Linux filesystem and the Docker runtime environment, which are essential for the operation of TorizonCore Builder.

For environments where WSL 2 cannot be used, it might be worth considering setting up a dedicated Linux virtual machine on your Windows 10 host. This way, you can still leverage the capabilities of TorizonCore Builder without directly using WSL 2. Virtualization platforms like VMware or VirtualBox could be used for this purpose, allowing you to run a Linux distribution that meets the requirements for TorizonCore Builder.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

[‘TorizonCore Builder Tool - Customizing Torizon OS Images | Toradex Developer Center’].

How did you like my response?
:+1: :-1:

Greetings @ducnn,

Just to chime in, what the AI bot here is saying about TorizonCore Builder is more or less correct. There are just too many Linux dependencies and requirements for the tool to run on a straight Windows environment. Some of these requirements/dependencies don’t even have Windows equivalents/substitutes as far as I’m aware.

Out of curiosity if you could share what limitations does your company impose on the use of WSL? Such information could be useful feedback for us if you don’t mind.

Best Regards,

Hi Jeremias,
The first thing I can say is the WSL does not have access to the company network. SSH and Ping from WSL cannot reach the destination.
Therefore, the torizoncore builder deploy does not work.

I can see the script and docker alias. I believe that it should have some PowerShell equivalents.

I believe that it should have some PowerShell equivalents.

I don’t believe you’re seeing the full picture here. As I said TorizonCore Builder has major components that do not have Windows functionality. For example OSTree is a major component in how the tool works. OSTree only works on Linux-based systems. Throughout the entire code-base of the tool we assume a Linux environment that behaves like standard Linux.

If you believe you can add PowerShell functionality to the tool then feel free to make a contribution. TorizonCore Builder is open-source and outside contributions are considered and merged if appropriate: GitHub - toradex/torizoncore-builder: TorizonCore Builder is a tool that allows the customization of TorizonCore images.

That said it would be far more straightforward if you could either use WSL or a Linux-based VM instead of a Windows environment.

Best Regards,

Hi Jeremias,

That is okay. If there is no easy way to make TorizonCore Builder work on PowerShell, I need to discuss it with our IT department to see what we can do.

Best regards,

If you can, please share what you end up doing here. Your solution may assist others with similarly restrictive company environments.

Best Regards,

There’s something very wrong with your WSL2 setup. Haven’t used Torizon-Builder, but I am using Yocto for our builds from within WSL2 without issues. Just out of curiosity:

$ uname -a
Linux XXXX-HPZ2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=54 time=13.9 ms
64 bytes from icmp_seq=2 ttl=54 time=13.3 ms
--- ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 13.298/13.600/13.903/0.302 ms

$ ssh xxx@192.168.xx.yy
xxx@192.168.xx.yy's password:

Hi Jeremias,

For building Yocto, the current plan is to use VM as you suggested. We will move it to GitHub Actions.
For upgrading and deploying, we have to use Recovery mode and Easy Installer.

Best regards,

Hi Logosol,

I am not sure what you mean.
WSL2 is not recommended by our company policies. I googled it and found out that many companies do block WSL. For example: WSL in Company Environment - Block WSL2 Company-Wide · Issue #10381 · microsoft/WSL · GitHub

Best regards,

Hi @ducnn
the github issue seems related to the lack of Windows Defender on WSL2.
But this post of some days ago shows some updates on the topic (as far as I understand).

1 Like


My comment was referring to this statement in your original post:

SSH and Ping from WSL cannot reach the destination.

All I wanted to say is that WSL (both 1 and 2) can have access to outside world if allowed to. You (or your manager) have to put your foot with your IT department that you need either unrestricted WSL2, or (better yet) native Linux computer for development.