wsl?

[WillEhrendreich]

I'd like to use this with wsl, is this possible?

is there anything in principle that would make this too much of a hassle? I'm already intimidated by linux and can't switch over completely, I just want a nice Lazyvim style experience where the craziness is smoothed over.

[tighthead3]

try windows hyper v manager, the built in windows VM manager. I have been running Omarchy as VM and playing with it like adding in Brave/Proton Mail etc. I'm new to linux as well and find this the best option to learn. I'm close to going bare metal since this is way less complicated than i thought. Follow DHH's manual and it will be a breeze. My only caveat is the sound settings haven't been configured thru hyper v manager for now. I have dual monitors with Windows on left and Omarchy on rights. If you're wanting to code just use github repo between wsl and vm

[rosscondie]

As far as I know WSL is interacting with the terminal and I am not sure about using it with a DE (desktop environment). According to some reddit posts it seems like it's possible to use some GUI applications and install a DE but seems like a hassle. If you want to use Omarchy or test it out it would be better to do it in a VM or bare metal if you have spare hardware.

In regards to having a good lazyvim setup, this will run just fine in the terminal on WSL/WSL2 out the box on a fresh install if that is all you are interested in having? Omarchy just happens to use Lazyvim as it's default Neovim.

[WillEhrendreich]

yeah, what i meant was like, the curated sane default experience of lazyvim as a base, which is the same idea behind omarchy, as far as i can tell. :)

[sailoz]

If you still wants to install Omarchy within Windows:
Here is a guide to install Omarchy with Hyper-V #445

[nunix]

It's possible to have Omarchy on WSL2, however it would be (very) targeted at the terminal apps.
This is particularly due to the default Hyprland tiling mode, which will not be applied to the WSL2 Wayland default display manager.

That being said, I went through the install file, and there would need quite some adaptation work to be done.
In a first "shotgun approach", here's what could get you started:

• Install Arch on WSL2: wsl --install --distribution archlinux --name omarchy
• Create a new user: useradd -m -s /bin/bash [username]
• Change both Root and User passwords: passwd && passwd [username]
• Install mandatory packages: pacman -Syu sudo base-devel wget vi
• Add USER to the sudoers file: echo "[username] ALL=(ALL:ALL) ALL" > /etc/sudoers.d/[username]
• Set your USER as default for the distro:

# Edit the WSL config file
vi /etc/wsl.conf

# Systemd should be there already, add these line before it
## Replace [username]
[user]
default = [username]

• Exit and terminate the session: wsl --terminate omarchy
• Launch a new session: wsl -d omarchy

From here, you can follow the initial instructions in https://omarchy.org/install, by installing git and cloning the repo (remember: do it in your WSL filesystem to avoid performances issues).

Edit the file ~/.local/share/omarchy/install.sh and comment/delete the following lines (not applicable to WSL):

# source $OMARCHY_INSTALL/config/network.sh
# source $OMARCHY_INSTALL/config/power.sh
# source $OMARCHY_INSTALL/config/login.sh
# source $OMARCHY_INSTALL/config/nvidia.sh

# source $OMARCHY_INSTALL/development/firewall.sh

# source $OMARCHY_INSTALL/desktop/bluetooth.sh
# source $OMARCHY_INSTALL/desktop/asdcontrol.sh

You can run the modified installer with bash ~/.local/share/omarchy/install.sh and follow the instructions.
"Normally" you'll get an error with xdg-settings for chromium.desktop. Need more work, but you can discard it as in recent WSL2 versions, you'll have your Windows browser opening with xdg-open [url].

Again, really not optimal as Omarchy relies on the Hyprland experience, which you'll not get on WSL2, so the Hyper-V or any other virtual machine hypervisor would be best indeed.

However, is WSL2 is the way you want to go, then more work needs to be put in it and I would even recommend to have an omarchy.wsl distro file created, so everything would be pre-installed. But again, work to do 😉

Hope this helps.
The Corsair

[linghengqian]

So, should creating a .wsl distribution artifact be opened as a separate issue? That would at least help align the installation experience with that of Ubuntu WSL.