5 phút đọc
casosorg/casos: CasOS: a cloud operating system built on Kubernetes, Live Demo: https://demo.casos.net – Repository casosorg/casos. Mô tả: CasOS: a cloud operating system built on Kubernetes, Live Demo: https://demo.casos.net. 1214 stars, 87 forks, ngôn ngữ chính JavaScript, cập nhật 2026-08-18.
1. Repository làm gì?
A cloud operating system built on Kubernetes
Official Website: https://www.casos.net
Live Demo: https://demo.casos.net
CasOS is a cloud operating system built on Kubernetes. It embeds the Kubernetes API server, controller manager, and scheduler, so you do not need an existing Kubernetes cluster or a separate control plane — CasOS is the platform itself. Run a single binary and get a fully functional cloud OS with a built-in web UI.
Supported platforms: Linux, macOS, Windows
The installer downloads the matching archive from the latest GitHub release, unpacks the executable, and adds CasOS to your user PATH. On Linux and macOS, open a new shell or run the source command printed by the installer before running casos; the installer also prints the absolute executable path. On Windows, the current PowerShell session is updated immediately. Releases are x86_64 only: an Apple Silicon Mac and a Windows on ARM machine both get that build and run it under emulation, while an arm64 Linux host has to build from source. Open http://localhost:9000 after starting CasOS. Rerun the command to upgrade. Set CASOS_VERSION to a release tag such as v1.32.0 to install that version. Both installers read the same settings:
2. Dữ liệu và cấu trúc đáng chú ý
For a piped Linux or macOS install, pass installer variables to bash, not to curl:
PowerShell has no equivalent prefix syntax. iex runs the installer inside the current session, so set the variables as $env: entries on their own lines first:
Those entries outlive the install and would pin any later run in the same window, so clear the ones you no longer want:
Check what you ended up with, which is also what to quote in a bug report:
A released binary prints its tag, commit and build date; a binary you built yourself reports dev.
The uninstaller removes the binary and the PATH entry the installer added. Pass the same INSTALL_DIR you installed with, if it was not the default.
Your data directory is not deleted. It holds the SQLite databases, the control-plane TLS material and the key that decrypts stored SSH credentials, so removing it is a separate, deliberate step. The uninstaller prints the path and the exact command for it.
3. Khả năng ứng dụng và giới hạn
The macOS binaries are not notarized. The installer is unaffected because curl does not mark downloads with com.apple.quarantine, but a build fetched manually through a browser is quarantined and Gatekeeper refuses to run it — including the executable unpacked from a quarantined archive. Clear the attribute after such a download:
Edit conf/app.conf with your values:
SQLite is the default and stores CasOS business data in data/casos.db and Kubernetes state in data/kine/state.db. The data directory is ignored by Git and is writable when running the development command from the repository root. A binary that runs without conf/app.conf and without a dataDir environment variable falls back to the per-user data directory (~/.local/share/casos, ~/Library/Application Support/CasOS, or %LOCALAPPDATA%\CasOS) instead of a working-directory-relative path.
Breaking change: dataDir used to default to /var/lib/casos. It now defaults to ./data, which is resolved against the working directory of the CasOS process, so starting CasOS from a different directory points it at a different — and most likely empty — data directory. Besides the two SQLite databases, dataDir also holds the control-plane TLS material and the key that encrypts stored SSH private keys, so a service that loses track of it can no longer decrypt existing machine credentials. Set dataDir to an absolute path such as /var/lib/casos for any system installation, make sure the service user can write to it, and move an existing /var/lib/casos to the new location before restarting. CasOS logs the directory it resolved as casos data directory: on startup.
MySQL remains available by setting driverName=mysql, configuring dataSourceName and dbName, and optionally setting a complete kineEndpoint. Switching an existing installation from MySQL to SQLite starts with empty SQLite databases; existing MySQL data is not imported automatically.
The control-plane proxy accepts host:port, socks5://, and socks5h:// addresses. When socks5Proxy is set, CasOS fails requests that cannot use the configured proxy instead of silently falling back to direct access. Destinations matched by the CasOS process NO_PROXY environment variable continue to use direct access. When socks5Proxy is blank, CasOS follows HTTP_PROXY, HTTPS_PROXY, and NO_PROXY, and uses direct access when no environment proxy is configured.
Upgrade notice: the previous example default of 127.0.0.1:10808 has been removed. Set socks5Proxy explicitly before upgrading if that local proxy is a required control-plane dependency.
casdoorEndpoint decides how you sign in, and nothing else has to be set up:
On first start CasOS creates a single built-in account, admin, with the password 123, and signs you straight in so a fresh install has nothing to configure. That also means anyone who can reach the CasOS port is an administrator until you change that password. Open the account menu in the top-right corner, pick My Account, and set a real one before exposing CasOS beyond your own machine — the automatic sign-in stops the moment the password is no longer 123. There is no password recovery: if you lose it, delete the row from the user table in data/casos.db and restart CasOS to get the default account back.
Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.
Nguồn tham khảo: Xem bài gốc
