2,534
stars
422
forks
52
watchers
18,496
prs
1,954
issues
10
releases
README
Chromebrew The Missing Package Manager For Chrome OS Chat With Us [!NOTE] Discord is not currently syncing messages with Slack Overview Chromebooks with ChromeOS run a Linux kernel. The only missing pieces to use them as full-featured Linux distro were gcc and make with their dependencies. Well, these pieces aren't missing anymore. Say hello to Chromebrew! Prerequisites You will need a Chromebook with developer mode enabled. To do so, select your device on the ChromiumOS Wiki and follow the instructions listed there. [!WARNING] Please be aware of the fact that developer mode is insecure if not properly configured. [!TIP] Setting a password as instructed in the VT-2 login screen is recommended. It is also recommended to enable signed boot: bash sudo chromeos-setdevpasswd sudo crossystem dev_boot_signed_only=1 Supported Systems | Architecture | Supported? | |:------------:|:----------:| | x86_64 | Yes | | i686 | Yes\ | | armv7l | Yes | | aarch64 | Yes\\ | \ _We can only provide limited support for i686 since Google has discontinued support. Although we can no longer support GUI apps, we will try to continue to support CLI programs._ \\ _We currently only provide armv7l packages even if your chromebook has an aarch64 userspace. For more details, see issue 8044._ Installation [!IMPORTANT] The beta, dev, and Canary channels are not supported and should not be used with Chromebrew. Failure to take notice of this warning will cause major issues with your Chromebrew installation. See issue 2890 and the FAQ for more details. [!WARNING] On ChromeOS M117+, the Chromebrew installer will not work in crosh anymore due to the security changes introduced in ChromeOS M117. Open a VT-2 terminal session with Ctrl+Alt+- and login with the chronos user and password if set above. (if you are unable to do this, please have a second look at the prerequisites and make sure your Chromebook is in developer mode) Then run the installation script below: bash bash [ ...] Where available commands are: | Command | Description | |:-------------------:|:------------| | build | build package(s) from source and store the archive and checksum in the current working directory | | check | check packages(s) | | const | display constant(s) | | deps | display dependencies of package(s) | | diskstat | show statistics about disk space occupied by installed packages | | download | download package(s) to CREW_BREW_DIR (/usr/local/tmp/crew by default), but don't install | | files | display installed files of package(s) | | help | get information about command usage | | install | install package(s) along with dependencies after prompting for confirmation | | list | available, compatible, incompatible, essential, installed packages | | postinsta
Top issues
#8044🐞 aarch64 userspace is now appearing for some machines as of M110, so need to rebuild all packages for aarch64...38 comments · 2023-03-06#3049Wine is only 64 bit on x86_64, can't use 32 bit prefix neither WINEARCH=win3224 comments · 2019-01-03#11416🐞 Bug: Vivaldi browser just opens to a white window17 comments · 2025-02-25#14985🐞 Problem installing `freecad`14 comments · 2026-03-12#10395Incorrect package versions13 comments · 2024-09-01#20050🐞 Bug Too many requests - problematic host12 comments · 2026-10-28#14984🐞 Can't upgrade crew because of `ruby_cgi`12 comments · 2026-03-12#16635🐞 Mesa conflicts with Libminigbm10 comments · 2026-06-02
Discussions
#16164Chromebrew working on ChromeOS dev channel0 comments · 2026-05-12#13849fix the dihcord1 comments · 2025-12-15#12273Supporters of Chromium-Based Operating-Systems . . .1 comments · 2025-07-27#12031WHEN CHROMEBREW WILL BE FULLY FIXED?1 comments · 2025-06-12#120172025 issues.1 comments · 2025-06-11#12005VSCODE on chromeos.1 comments · 2025-06-09#11404How would I get a desktop environment2 comments · 2025-02-24#11179Contributing packages to Chromebrew1 comments · 2025-01-23