Installation Guide
This page provides a detailed installation guide for MANYOYO, including prerequisites, installation steps, and image building.
Recommended: one-line install
On macOS and Linux (Debian / Ubuntu) prefer the one-line install; macOS needs no administrator password, and on Linux sudo is only used to install a missing container runtime, and only with your consent. The npm / package manager / source methods below are for Windows (WSL), and for users who already have Node.js and Docker / Podman and want to manage versions themselves.
System Requirements
Required
- Node.js >= 22.0.0
- Docker or Podman (Podman recommended)
Recommended
- Disk Space: At least 10GB available (for images and cache)
- Memory: At least 4GB RAM
- Network: Stable network connection (required for downloading dependencies on first build)
Verify Prerequisites
Before installing MANYOYO, confirm that required software is installed:
# Check Node.js version (requires >= 22.0.0)
node --version
# Check npm version
npm --version
# Check Docker or Podman
docker --version # or
podman --versionIf not installed, please install these software first:
Install Node.js
macOS/Linux:
# Using nvm (recommended)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
nvm install 22
nvm use 22
# Or using system package manager
# macOS
brew install node@22
# Ubuntu/Debian
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
sudo apt-get install -y nodejsWindows (Native):
- Download installer from Node.js official website (best for PowerShell/native Windows workflow)
Windows (WSL2):
- In WSL2, use the Linux-style installation flow, preferably
nvm(best for Bash/Linux workflow)
# Run inside WSL terminal
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
nvm install 22
nvm use 22Install Podman (Recommended)
macOS:
brew install podman
# Initialize Podman machine
podman machine init
podman machine startLinux:
# Fedora/RHEL/CentOS
sudo dnf install podman
# Ubuntu/Debian
sudo apt-get update
sudo apt-get install podman
# Arch Linux
sudo pacman -S podmanWindows:
- Download installer from Podman official website
Install Docker (Optional)
If choosing to use Docker instead of Podman:
macOS/Windows:
- Download Docker Desktop
Linux:
# Ubuntu/Debian
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
# Add user to docker group
sudo usermod -aG docker $USER
newgrp dockerInstall MANYOYO
Global Installation (Recommended)
Install MANYOYO globally using npm:
npm install -g @xcanwin/manyoyoNon-root Global npm Install (macOS/Linux/WSL)
If npm install -g xxx fails with EACCES / permission denied, use a user-owned global prefix instead of sudo:
mkdir -p "$HOME/.npm-global"
npm config set prefix "$HOME/.npm-global"
echo 'export PATH=$HOME/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrcNotes:
- This permission issue is common on macOS/Linux/WSL when Node.js uses a system-owned prefix (for example
/usr/local) - Native Windows environment does not use
sudo - If you use zsh, append PATH in
~/.zprofileor~/.zshrc
After installation, verify:
# Check version
manyoyo -v
# View help information
manyoyo -hLocal Development Installation
If you need to install from source (for development or testing):
# Clone repository
git clone https://github.com/xcanwin/manyoyo.git
cd manyoyo
# Install dependencies
npm install
# Global link (development mode)
npm install -g .
# Or use npm link
npm linkUpdate MANYOYO
npm update -g @xcanwin/manyoyo
manyoyo -vVerify Installation
manyoyo -v # version
manyoyo init all # migrate existing claude/codex/gemini/opencode host config (recommended)
manyoyo run -n test-container -x echo "MANYOYO works!" # create and run a test container
manyoyo ps # list containers
manyoyo rm test-container # remove the test container
manyoyo run -r claude # use the initialized run configThe default image is pulled automatically on first use; you only need to build for a custom image, see Custom Image. For install or run errors, see Troubleshooting and Build Issues.
Upgrade and Uninstall
Upgrade the image: after building a new tag for a custom image, set imageVersion in ~/.manyoyo/manyoyo.json to "2.2.0-common", then run manyoyo prune to remove dangling images.
Uninstall an npm-installed MANYOYO:
npm uninstall -g @xcanwin/manyoyo
manyoyo ps && manyoyo rm <name> # remove containers one by one after checking names (optional)
rm -rf ~/.manyoyo/ # delete config, history and logs (optional, irreversible)For offline-package installs, use manyoyo update and manyoyo uninstall, see Install.
Offline Package Layout
For maintainers and anyone curious about what is inside. The one-line installer scripts/install.sh only downloads, verifies and starts the .run; the real installation logic is install/install.sh inside the unpacked .run.
- Assets on a Release: for each platform (
macos/linux) × chip (arm64/x64) there is one installermanyoyo-<version>-<os>-<arch>.runand one upgrade packagemanyoyo-<version>-<os>-<arch>-app.tar.gz, plus one checksum listSHA256SUMS, 9 files in total. The-app.tar.gzis downloaded bymanyoyo updateautomatically (only Node.js and manyoyo, tens of MB); you normally do not need to download it; if GitHub is unreachable, download it withSHA256SUMSinto the same directory and install it withmanyoyo update --file <package>. - Self-verification: the
.runverifies itself before installing. To only verify without installing:sh manyoyo-*.run --check; to list the contents:--list; to unpack into a directory only:--extract <dir>. - Compare checksums by hand:
grep "$(shasum -a 256 manyoyo-*-macos-arm64.run | cut -d' ' -f1)" SHA256SUMS; one line with the file name means a match. - Read the script before running it:
sed -n '1,/^__MANYOYO_PAYLOAD_BELOW__$/p' manyoyo-*.run. - Volumes: a file is split into
.run.001,.run.002, ... only when it would exceed GitHub's 2 GiB limit. Download all of them into one directory and runsh manyoyo-*.run.001; the installer joins and verifies them itself. You can also merge by hand withcat manyoyo-*.run.* > manyoyo-merged.runand use it as a normal.run. - Install location:
~/.manyoyo/app/<version>/holds the program,app/currentpoints to the active version; upgrades switch it atomically and keep the previous version forupdate --rollback.
Next Steps
- Install: one command to get set up
- Basic Usage: common commands and operations
- Configuration System: environment variables and config files