# Install Omarchy Linux on M1/M2 Mac.. in a virtual machine. Easy Peasy **URL:** \ **Category:** Random\ **Created:** [August 27, 2026, 12:37am UTC](https://forum.pinegrow.com/t/install-omarchy-linux-on-m1-m2-mac-in-a-virtual-machine-easy-peasy/12009 "2026-08-27T00:37:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\ **Post date:** [August 27, 2026, 12:37am UTC](https://forum.pinegrow.com/t/install-omarchy-linux-on-m1-m2-mac-in-a-virtual-machine-easy-peasy/12009/1 "2026-08-27T00:37:19Z")
Unless you DONT have a Spanish Keyboard that is… I dont , so it was a bit.;. tricky for a bit. (hours actually) As, I have a GB English one. so lets begin. and explain that issue at the end. History. Omarchy Linux Its here > **[Omarchy](https://omarchy.org/)** > > Beautiful, Modern & Opinionated Linux by DHH and is **Omarchy: the Linux distro built for the agentic AI age** So, since PineGrow has gone _all Ai_ _ **Flavoured,** …_ This might be of interest around here. check this out if you live under a rock.. with WiFi. > **[Omarchy: the Linux distro built for the agentic AI age](https://tbreak.com/omarchy-linux-distro-agentic-ai/)** > > Omarchy is the Arch-based Linux distro with an AI agent built in. Here is the field it leads, from Ubuntu 26.04 to CachyOS, and how to try it. Omarchy Linux is Based on ARCH linux (EEK historically the most difficult to install) and runs native on BARE METAL.. on an Apple Silicon M1/2 Mac ( M1 and M2 works, M3 under development, any newer and your out of luck)), BUT, it CAN’T dual boot.. so wipes your Mac OS. .. And moves into you Apple Silicon house.. thank you very much.. Replacing Mac OS altogether. er, No! SO how about a Virtual machine? Oh Go on then! You persuaded me. bring on UTM! > **[UTM](https://mac.getutm.app/)** > > Securely run operating systems on your Mac wow. Virtalization Or Emulation. SO install UTM, on your SIlicon Mac (Currently this is the only way to go about this Omarchy Install on this ARM architecture.) it even comes with a gallery of links to pre built .UTM image files you can download and install in your Virtualised environment, on your mac… > **[Gallery](https://mac.getutm.app/gallery/)** > > Virtual machines for Mac but, there isn’t one for Omarchy as… the actual developer of it, hasnt built one… Well, there was version 3 of Omarchy which said NO ARM Macs (Intel ok), But now there is Version 4 which doesn’t have that stipulation but, the installer is broken when it comes to grabbing libraries, URLs etc during installs and fails. which is explained VERY well, by this Spanish chap … remember the keyboard issue? well, yeah… your going to find out about that. So this chap.. Developer God mode engaged… has Created a _fixed_ Omarchy .UTM image file (the ones which arent in the Gallery) And tells you about it here → > **[GitHub - ggalancs/omarchy-arm-utm: Omarchy 4 (quattro) on Arch Linux ARM — a native...](https://github.com/ggalancs/omarchy-arm-utm)** > > Omarchy 4 (quattro) on Arch Linux ARM — a native aarch64 UTM VM for Apple Silicon, built from macOS by one script And he has created the FIXED .UTM Omarchy m1/m2, Apple Silicon, ARM Omarchy linux install image file available… here > **[Omarchy 4 on Arch Linux ARM — UTM virtual machine for Apple Silicon : Gabriel...](https://archive.org/details/omarchy-arm-utm)** > > DOWNLOAD omarchy-arm-utm-v2.zip (3.6 GB) — it supersedes the original 6.5 GB file. See VERSIONS.md. A ready-to-run UTM virtual machine: Arch Linux ARM... … its … sloooooooooooow. TO download! I opted to download the latest version 4 of Omarchy (Config files are in .lua format, Omarchy 3 are .config) via torrent. the torrent contains BOTH versions. Using the Torrent client I was able to inspect the torrent and download ONLY the V2 of the image (the smaller 3.x GB installer Image.- the older version 3, has some install bugs and is nearly twice the size) It’s a zip file… when it Finallly downloads, you have. **omarchy-arm-utm-v2.zip** unzip it… you now have … **Omarchy ARM.utm** Now… double click it. **BANG!** UTM program opens up and… in and incredibly short moment (maybe a minute?) You have a fully functioning, configured installed Virtualisation of Omarchy Linux, Running in UTM. .. thats it! its done! oh wait. did I mention the keyboard? ah yes… … so, I have a _Spanish_ ghost in the machine, I will have to address. So you will be presented with …well a pretty screen saver and basically … NOTHING! else. until you press Option + Space. then a menu pops up. ![Screenshot 2026-08-27 at 01.50.38](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/2/29e5eea5cab2d649caab27530b234f81279a9574.jpeg) THIS…is how you navigate… Keystrokes! Just check out _key bindings **Opt + k** _ ![Screenshot 2026-08-24 at 19.07.27](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/2/26ecf2c7cc0df5636e40a9f77fc680040ac4a486.png) ![Screenshot 2026-08-27 at 01.50.38](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/2/29e5eea5cab2d649caab27530b234f81279a9574.jpeg) So I selected Setup and then… _Input_ ![Screenshot 2026-08-27 at 02.00.43](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/0/0665c0cd6b02f1fb279420ea27ce2eb259a8110c.jpeg) And now I could work my input, keyboard adjusting magic now, say you want to change some settings (for me… the Monitor Resolution) … you click Monitor… and.. oh , dear god! Welcome to Arch… Linux. You’re now greeted by a .lua config file … which you now have to edit…\> In… **NeoVIm. (for me, sad face)** so… to do this… You click i … to enter insert mode and then… oh no what the hell? I cant find the characters? what , is my keyboard broken? OH! NO!? … i was writing gobbledegook! all sorts of accented letters. it took me a while to try and figure this out. as I needed to edit the Monitor file resolution and use ( ) { } " symbols and instead I got… ) = ^ \* Ñ now! that last one was a peach! But led to me figuring out how to do this. The developer’s other docs are in Spanish… So I figured out that maybe what had gone pear shaped, as in his Github brief of what he’d created and how it worked , he said, _It asks six values that it pre-fills from your Mac — timezone from `/etc/localtime`, keyboard from macOS preferences, cores and RAM from `sysctl`_ So I figured he’s built this with HIS keyboard, which was Spanish… I couldnt get Copy and paste to work between Host and Guest OS (Linux Clipboards…Buffers, Ill work it out) And I couldnt remember how to use NeoVIm, but I KNEW i needed the **:** to enter into Save mode… after editing, after using i for insert mode in NeoVIm, in order to edit it… and instead I got… **Ñ** curses! So I hunted around and found this Useful site. > **[Spanish Keyboard Layouts](http://xahlee.info/kbd/spanish_layout.html)** WHAT characters were where on a Spanish Keyboard and … where the ones I actually needed were! its this one, the SPANISH keyboard -the 2nd Image.. as the 1st is LATIN AMERICAN Spanish… … Sheesh! So thank you to Xah Lee, for Creating that online info page. ![Screenshot 2026-08-27 at 01.01.05](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/f/f7f86f9fc4f73c4089cad88aced12f30b4d99bdc.jpeg) SO I could now type all the wrong characters on my physical keyboard and see the correct ones appear in the config file and then :wq to Save and quit the .lua config file… 2… TWO… and a half hours. Because I then had to edit the keyboard one… to set it to English… when I COULDNT type the characters… in order to .. set my keyboard … to English and Mac using ```auto hl.config({ input = { -- Set the primary layout to GB kb_layout = "gb", -- Optional: Add variants or multiple layouts (e.g., "gb,us") kb_variant = "mac", -- Optional: Configure switching options if using multiple layouts -- kb_options = "grp:alts_toggle" }, }) ``` So there is a morning of my life I will never get back, but, Once I Edited the Keyboard config , saved and exited, It was VERY satisfying. but .\> Neovim.. I mean, check this out… TRY and find… the save command .. here. > **[Editing](https://neovim.io/doc/user/editing/)** > > hyperextensible Vim-based text editor try searching that page for .. _save_… good luck! A clue, Try searching it for **:wq** I know!! Obvious right, yeah? where you will find it buried in _When writing the buffer, the default is to use the current file name. Thus when you give the “ZZ” or “:wq” command, the original file will be overwritten. If you do not want this, the buffer can be written into another file by giving a file name argument to the “:write” command. For example:_ This is Better! > **[Basic Editing Operations - Neovim](https://mintlify.wiki/neovim/neovim/user-guide/basic-editing)** > > Learn the fundamental editing operations in Neovim Id also tried adding the Spanish Language Keyboard to my Host Mac OS, Turning on Accessibilty, Enabling Pop UP Visual Keyboard under _Motor_ setion… AAAAnd… Fail. ![Screenshot 2026-08-26 at 09.43.51](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/4/466f5ce0dfb8ed22424ec1b68c1741610ccc43b0.jpeg) and then … I stared at the blanks wallpaper, filled with trepidation. so, if you want to experience that _liberating experience_ like I did and set up an **Agentic Centric** LInux OS on you M1/2 Mac in a virtual machine… 1. Install UTM > **[UTM](https://mac.getutm.app/)** > > Securely run operating systems on your Mac 1. Download the OMARCHY V4 .utm image file… (which is helpfully labelled V2.. as the zipped file in the torrent- as the original image in the download is Omarchy V3). > **[Omarchy 4 on Arch Linux ARM — UTM virtual machine for Apple Silicon : Gabriel...](https://archive.org/details/omarchy-arm-utm)** > > DOWNLOAD omarchy-arm-utm-v2.zip (3.6 GB) — it supersedes the original 6.5 GB file. See VERSIONS.md. A ready-to-run UTM virtual machine: Arch Linux ARM... … takes ages. then double click the V2 .UTM file. BOOM Its installed and running. UNLESS YOU’RE USING A SPANISH KEYBOARD.. edit the config file to change /add your keyboard to the System config file. (See the whole sketch above) And thats it. Im now exploring Combining Ollama with Hermes Agents to see if I can get that combo to DO things in this new Linux OS, not just chat to an LLM in Ollama. have fun! Docs are here for V3 > **[The Omarchy 3 Manual](https://learn.omacom.io/2/the-omarchy-manual)** > > Preserved for legacy installations of Omarchy. Find Omarchy Quattro (v4) manual on omarchy.org. more > **[Dotfiles](https://omarchy.org/manual/dotfiles/)** > > Omarchy is primarily configured through the so-called dotfiles that live in ~/.config. Those are considered your files for your changes. The files that live... Watch the Video here [![](https://img.youtube.com/vi/F7fe9pa8OeE/maxresdefault.jpg "Omarchy Quattro") ](https://www.youtube.com/watch?v=F7fe9pa8OeE) or… You could just build it yourself. > **[GitHub - ggalancs/omarchy-arm-utm: Omarchy 4 (quattro) on Arch Linux ARM — a native...](https://github.com/ggalancs/omarchy-arm-utm#quick-start-build-it-yourself)** > > Omarchy 4 (quattro) on Arch Linux ARM — a native aarch64 UTM VM for Apple Silicon, built from macOS by one script This Image Creators explanation and walkthrough of the process he went through and description of all the broken stuff and fixes is a masterclass in documentation.. IN my opinion anyway. **OH! AND GET USED TO PRESSING OPT+CTRL .. a lot! to make sure your your mouse is _Captured_** ok Ciao. This took ages to write, to hopefully make this look accessible and easy… Along with my big keyboard issue 🙂 Ok Ciao.. or. in this case.. Adios! ---
**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\ **Post date:** [August 28, 2026, 10:20am UTC](https://forum.pinegrow.com/t/install-omarchy-linux-on-m1-m2-mac-in-a-virtual-machine-easy-peasy/12009/2 "2026-08-28T10:20:51Z")
ah! Well… that wasnt all plain sailing was it… Sigh… > > > \### Summary > > Omarchy's install paths name packages that only exist for \`x86\_64\`,… and nothing in > the tree checks the running architecture, so on aarch64 the \*\*Install\*\* menu offers > entries that can never succeed. Each one fails in a floating terminal that prints > \`error: target not found: \\` and closes, usually faster than it can be read. > > \### System details > > \- Omarchy \`4.0.0.alpha\` (from \`/usr/share/omarchy/version\`) > \- Arch Linux ARM, \`uname -m\` = \`aarch64\`, kernel \`7.2.0-2-aarch64-ARCH\` (not Asahi) > \- QEMU/UTM guest on an Apple Silicon host (\`product\_name\` = \`QEMU Virtual Machine\`, > \`/proc/device-tree/compatible\` empty) > \- pacman repositories configured: \`core\`, \`extra\`, \`alarm\`, \`aur\` > > \### Mechanism > > Three pieces combine: > > 1. \*\*\`bin/omarchy-pkg-add\` is pacman-only.\*\* It runs > \`sudo pacman -S --noconfirm --needed "$@"\` and never touches the AUR > (\`bin/omarchy-pkg-aur-add\` is the separate \`yay\` path). Any name that is not in a > configured sync repository fails outright. > 2. \*\*\`bin/omarchy-install-app\` hides the failure.\*\* It wraps \`omarchy-pkg-add\` in > \`omarchy-launch-floating-terminal-with-presentation\`, so the pacman error appears > in a transient floating window and disappears. The same is true of every > \`omarchy-launch-floating-terminal-with-presentation omarchy-install-\*\` menu action. > 3. \*\*Nothing anywhere checks the architecture.\*\* In 4.0.0.alpha, > \`grep -rIn 'x86\_64\\|aarch64\\|uname -m\\|arm64\\|HOSTTYPE\\|MACHTYPE' bin default install config etc shell\` > returns no hits. The \`omarchy-hw-\*\` predicate family covers CPU vendor, GPU, > chassis and peripherals, but has no architecture predicate, so no menu entry can > currently gate on one. > > The \`\[omarchy\]\` repository compounds this. \`default/pacman/pacman-stable.conf\` points > it at \`https://pkgs.omarchy.org/stable/$arch\`, and that tree is x86\_64-only: > > \`\`\` > $ curl -o /dev/null -w '%{http\_code}\\n' https://pkgs.omarchy.org/stable/x86\_64/omarchy.db > 200 > $ curl -o /dev/null -w '%{http\_code}\\n' https://pkgs.omarchy.org/stable/aarch64/omarchy.db > 404 > \`\`\` > > Most of the AUR-derived apps in the Install menu resolve out of \`\[omarchy\]\` on x86\_64 > (\`1password\`, \`cursor-bin\`, \`dropbox\`, \`lmstudio-bin\`, \`once-bin\`, > \`openai-codex-desktop\`, \`spotify\`, \`sublime-text-4\`, \`symfony-cli\`, > \`visual-studio-code-bin\`, \`voxtype-bin\`, … — 202 packages in the x86\_64 database), so > on aarch64 they have no source at all through the pacman-only path. > > \### Reachable entries whose package cannot exist on aarch64 > > Every row below is offered from \*\*Menu → Install\*\* with no hardware or architecture > gate. Their only \`disabled\` predicate is \`omarchy-pkg-present \\`, which is false on > a machine where the package could never have installed — so the entry renders enabled. > \`arch=\` values are from the authoritative PKGBUILD at > \`https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=\\`; "not in any repo" was > checked with \`pacman -Si\` against \`core\`/\`extra\`/\`alarm\`/\`aur\`. > > | Menu path | Command it runs | Package | Why it fails on aarch64 | > | --- | --- | --- | --- | > | Install → AI → Ollama | \`omarchy-install-app Ollama ollama\` | \`ollama\` | AUR \`arch=('x86\_64')\`; not in any aarch64 repo. \*\*Reproduced on this host\*\* — \`/var/log/pacman.log\` \`\[2026-08-27T20:41:18+0300\] \[PACMAN\] Running 'pacman -S --noconfirm --needed ollama'\`, \`error: target not found: ollama\`. Ollama does publish \`ollama-linux-arm64.tar.zst\` upstream, so this is a packaging assumption rather than a support gap. | > | Install → AI → LM Studio | \`omarchy-install-app 'LM Studio' lmstudio-bin\` | \`lmstudio-bin\` | AUR \`arch=('x86\_64')\` | > | Install → Editor → Cursor | \`omarchy-install-and-launch Cursor cursor-bin cursor\` | \`cursor-bin\` | AUR \`arch=('x86\_64')\` | > | Install → Editor → Zed | \`omarchy-install-editor-zed\` → \`omarchy-pkg-add zed omazed\` | \`zed\`, \`omazed\` | no aarch64 \`zed\` in \`extra\`/\`alarm\`; AUR \`zed\` is \`arch=('x86\_64')\`. \`omazed\` is \`arch=('any')\` but AUR-only, which the pacman-only path cannot reach. | > | Install → Service → 1Password | \`omarchy-install-service-1password\` → \`omarchy-pkg-add 1password 1password-cli\` | \`1password\` | AUR \`arch=('x86\_64')\` (\`1password-cli\` does list \`aarch64\`) | > | Install → Service → Spotify | \`omarchy-install-service-spotify\` → \`omarchy-pkg-add spotify\` | \`spotify\` | AUR \`arch=('x86\_64')\` | > | Install → Service → Dropbox | \`omarchy-install-service-dropbox\` → \`omarchy-pkg-add dropbox …\` | \`dropbox\`, \`nautilus-dropbox\` | AUR \`arch=("x86\_64")\` for both | > | Install → Development → PHP → Symfony | \`omarchy-install-dev-env symfony\` → \`omarchy-pkg-add symfony-cli\` | \`symfony-cli\` | AUR \`arch=('x86\_64')\` | > | Install → Browser → Edge | \`omarchy-install-browser edge\` → \`omarchy-pkg-aur-add microsoft-edge-stable-bin\` | \`microsoft-edge-stable-bin\` | AUR \`arch=('x86\_64')\` — fails in \`yay\` rather than pacman, but is equally unreachable | > > \### Reachable entries whose package \*could\* work on aarch64 > > These are a milder case of the same mechanism: the upstream PKGBUILD does list > \`aarch64\`, but the package lives only in the AUR and in \`\[omarchy\]\`, and > \`omarchy-pkg-add\` is pacman-only while \`pkgs.omarchy.org\` has no aarch64 tree. So they > fail too, even though nothing about them is architecture-bound. > > | Menu path | Package | Upstream \`arch=\` | > | --- | --- | --- | > | Install → AI → ChatGPT Desktop | \`openai-codex-desktop\` | \`('x86\_64' 'aarch64')\` | > | Install → Editor → VSCode | \`visual-studio-code-bin\` | \`('x86\_64' 'aarch64' 'armv7h')\` | > | Install → Editor → Sublime Text | \`sublime-text-4\` | \`('x86\_64' 'aarch64')\` | > | Install → Service → ONCE | \`once-bin\` | \`('x86\_64' 'aarch64')\` | > | Install → Service → NordVPN | \`nordvpn-bin\` | \`('x86\_64' 'i686' 'armv7h' 'aarch64' 'armeabi')\` | > > \### What is \*not\* affected > > For completeness, I traced every x86-only package name in \`bin/\`, \`install/\` and > \`default/\` and confirmed the following are correctly gated behind an \`omarchy-hw-\*\` > predicate or a hardware-detection guard, so they never run on ARM and are \*\*not\*\* part > of this report: \`intel-lpmd\`, \`thermald\`, \`intel-media-driver\`, \`libvpl\`, \`vpl-gpu-rt\`, > \`libva-intel-driver\`, \`intel-ipu7-camera\`, \`linux-ptl\`, \`linux-ptl-headers\`, > \`sof-firmware\`, \`asusctl\`, \`supergfxctl\` (\`when: omarchy-hw-hybrid-gpu\`), > \`broadcom-wl\`, \`macbook12-spi-driver-dkms\`, \`dell-xps-touchpad-haptics\`, > \`dell-xps13-sidecar-amps\`, \`qmk-hid\`, \`tuxedo-drivers-nocompatcheck-dkms\`, > \`yt6801-dkms\`, \`linux-firmware-marvell\`, the \`nvidia.sh\` kernel/driver set, and the > \`ollama-cuda\` / \`ollama-rocm\` branches of \`install.ai.ollama\` (guarded by > \`omarchy-cmd-present nvidia-smi\` / \`rocminfo\`). > > I also deliberately left the gaming entries (\`install.gaming.steam\`, > \`.lutris\`, \`.heroic\`) out of the tables. They are ungated and they do fail > (\`steam\` is multilib-only, \`wine-staging\` is \`arch=('x86\_64' 'i686')\`, > \`heroic-games-launcher-bin\` is \`arch=('x86\_64')\`), but the whole stack is x86-bound by > nature and arguably belongs to a different discussion. > > One adjacent case I could not classify cleanly and am flagging as \*\*unverified\*\*: > \`install.gaming.xbox-controllers\` runs \`omarchy-pkg-add linux-headers xpadneo-dkms\`. > \`xpadneo-dkms\` is \`arch=(any)\`, but \`linux-headers\` does not exist under that name on > ALARM (\`linux-aarch64-headers\`) or Asahi (\`linux-asahi-headers\`). That is a kernel > package-naming assumption rather than an architecture one, and several > hardware-gated scripts share it. > > \### How this differs from the existing reports > > \- \*\*#8530\*\* and \*\*PR #8316\*\* address the Voxtype install path specifically, and #8316 > is the right shape for it — a source-build fallback gated on the new > \`omarchy-hw-x86-64-v3\` predicate. But that fix is local to > \`bin/omarchy-voxtype-install\`; the same class of failure remains in every other > ungated Install entry above. > \- \*\*#7883\*\* and \*\*PR #8149\*\* cover the related AVX2/SSE4.2 baseline problem \*within\* > x86\_64. > \- \*\*PR #8039\*\* covers the aarch64 \*install-time\* path (\`mkinitcpio\` \`thunderbolt\`, > \`\[multilib\]\` in \`pacman.conf\`, \`mise-work\`) and notes the \`pkgs.omarchy.org\` aarch64 > gap as out of scope. This issue is about the post-install, user-facing menu. > \- \*\*#87\*\* (closed) and \*\*#803\*\* (closed) are much older and predate the current menu. > > I did not find an open report covering the general case. > > \### Suggested direction > > Offered as options, not a prescription: > > 1. \*\*A preflight in \`omarchy-pkg-add\`.\*\* Before shelling out to pacman, check that each > name resolves for the running architecture and, when it does not, fail with a > message that says so — instead of letting \`error: target not found\` scroll past in a > window that closes. This would cover every call site at once, including the ones > reached from scripts rather than the menu. > 2. \*\*\`disabled\` predicates on the menu entries\*\* whose package cannot exist on the > running architecture, so the entry is greyed out rather than offered. PR #8316's > \`bin/omarchy-hw-x86-64-v3\` already returns false for any non-\`x86\_64\` machine > (\`\[\[$machine == "x86\_64" \]\] || exit 1\` before the flag checks), so it could serve as > that gate directly, or a narrower \`omarchy-hw-x86-64\` predicate could be split out of > it. > 3. \*\*Publishing an aarch64 tree on \`pkgs.omarchy.org\`\*\* would independently fix the > second table, since those packages already build for ARM. > > (1) and (2) are complementary: (2) keeps the dead entries out of the user's way, (1) > catches the script-level call sites and gives a readable error when a package is missing > for any other reason. > > Happy to open a PR for whichever of these you'd prefer — the \`omarchy-hw-x86-64\` > predicate plus \`disabled\` gates is the smallest change, and the \`omarchy-pkg-add\` > preflight is the one that covers the most ground. I specifically installed that _Bleeding edge, ARM virtual version of Omarchy on the mac, in order to test out the_ _AGENTIC FIRST, AI driven nature of the beast_ well… it turns out… it DOESNT actually install the AI applications, using its Automated GUI Interface installer as…\> it directs the installer to intel x86\_64 arch linux library packages instead of the ARM ones for M1 Architecture. ugh! ---
**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\ **Post date:** [September 4, 2026, 6:52am UTC](https://forum.pinegrow.com/t/install-omarchy-linux-on-m1-m2-mac-in-a-virtual-machine-easy-peasy/12009/3 "2026-09-04T06:52:13Z")
OH! LInux as an App… on Mac!! here, you can run Linux.. on the mac… as… an app? what? AN OS as an App? Ive never seen this. > **[Release v0.1.0 · omacom/try-omarchy](https://github.com/omacom/try-omarchy/releases/tag/v0.1.0)** > > First Public Release 🎉 > Try Omarchy allows you to run the upstream Omarchy desktop as a self-contained, hardware-accelerated app on any Apple Silicon Mac. > Highlights > > Full keyboard support > High DPI ... I however… cant! As my Mac OS is too old.. grrr Im still running Mojave. SO if anyone tries this out, let me know how it goes. Download the DMG file, its about 1.2GB