# Computer Images **Page:** foundation/computers/images [Download Raw Markdown](./foundation/computers/images.md) --- # Computer Images Every computer starts from an image: the operating system, pre-installed software and default configuration it boots with. The platform carries one base image, Debian 13 (`debian/13`). The marketplace lists images too, both free community images and paid images that arrive pre-configured. Name the image in `computer_image` when you [create a computer](/foundation/computers/create-edit-delete/#image-selection): The format is `{os}/{release}`. A create accepts only `debian/13` (the shorthands `debian` and `debian-13` resolve to it), and uses `debian/13` when `computer_image` is omitted or null. Naming an unsupported image returns `400`. Use `debian/13`. That holds whatever your image library holds. In the Hub, open **Computers** and choose **Get a computer**. A new computer starts from Debian 13; the form shows **System** as **Debian 13**, with no other image choice. ## What does an image include? ``` Computer Image (Debian 13) ↓ Computer Creation ↓ Running Computer (Debian 13 + your work) ``` An image provides the base operating system (a Linux distribution), system libraries and tools, the default package manager (apt), the initial filesystem structure and sometimes pre-installed software such as databases, web servers or dev tools. Your work builds on top: install applications, configure services, add data and change the environment. - **Images are immutable templates.** Creating a computer from an image does not change the image. A computer's image is fixed once the computer exists; to start again from a clean base, see [Change the OS](/foundation/computers/create-edit-delete/reference/#change-the-os). - **Images do not include the Hoody Kit.** Its 20 HTTP services are installed when you create the computer with `hoody_kit: true`. ## Find an image in the marketplace Search the public marketplace by keyword. A search matches the image's alias, name and description: ```bash # Find Docker-related images hoody images list --search docker # Find database images hoody images list --search database # Find Node.js images hoody images list --search nodejs ``` ```typescript // Find Docker-related images const dockerImages = await client.api.images.listPublic({ search: 'docker' }); // Find database images const dbImages = await client.api.images.listPublic({ search: 'database' }); // Find Node.js images const nodeImages = await client.api.images.listPublic({ search: 'nodejs' }); ``` ```bash # Find Docker-related images curl "https://api.hoody.com/api/v1/images/public?search=docker" \ -H "Authorization: Bearer $HOODY_TOKEN" # Find database images curl "https://api.hoody.com/api/v1/images/public?search=database" \ -H "Authorization: Bearer $HOODY_TOKEN" # Find Node.js images curl "https://api.hoody.com/api/v1/images/public?search=nodejs" \ -H "Authorization: Bearer $HOODY_TOKEN" ``` Each link searches the public marketplace for a different keyword. Narrow the list by operating system, CPU architecture, price or rating, sort it and page through it with the [marketplace filters](/foundation/computers/images/reference/#marketplace-filters). Each image's architecture, size, price and ratings are in its [image fields](/foundation/computers/images/reference/#image-fields). ## Import or buy an image Your library holds the images you imported or bought. Today a library entry lets you list the image and rate it; a create still starts from `debian/13`. Most OS images are free. Import one into your library. With an auth token, importing or rating an image needs the `computers.create` permission, and listing your library needs `computers.read`; without it the call answers `403`: Some images include pre-installed commercial software and carry a price. Check the image details, price included, first: Buying deducts the price from your wallet balance. It is a one-time payment, and the image stays in your library. With an auth token, buying needs the `financial.wallet.transfer` permission; without it the call answers `403`: Your library lists the images you have imported or purchased: A create still names its base image in the `{os}/{release}` format, `debian/13`, whatever your library holds. The [responses](/foundation/computers/images/reference/#responses) and [refusals](/foundation/computers/images/reference/#common-questions) are in the reference. ## Rate an image Rate images honestly on the 0 to 5 scale. Ratings are what the next person sees when picking an image. You can rate an image in your library (import a free one first) with a whole number, and rating again replaces your earlier rating: What each number means: the [rating scale](/foundation/computers/images/reference/#ratings). ## Run Docker or Kubernetes inside a computer Hoody computers support Docker, Kubernetes and other container orchestration platforms. A computer created with `hoody_kit: true` gets the dev kit by default, and the dev kit already includes Docker Engine, Docker Compose and Docker Buildx. Nothing to install and nothing to start: the Docker daemon starts on the first `docker` command, and the default user can run `docker` without `sudo`. ```bash # In a computer created with hoody_kit (dev kit on by default) docker run hello-world docker compose up -d docker build -t myapp . ``` In a computer without the dev kit, install Docker Engine by following [Docker's installation guide for Debian](https://docs.docker.com/engine/install/debian/) and check that Docker is running. Run Docker commands with `sudo`, for example `sudo docker run hello-world`. To run them without `sudo`, follow Docker's [post-installation steps for non-root users](https://docs.docker.com/engine/install/linux-postinstall/) and start a new login session. What works: [Docker hosts](/foundation/computers/images/reference/#docker-hosts). Kind, Minikube and K3s each run a full Kubernetes cluster inside a Hoody computer, and Podman runs too. Each needs a short setup: [Kubernetes and Podman](/foundation/computers/images/reference/#kubernetes-and-podman). ## Build a reusable template You cannot create your own custom images through the API. Images and snapshots together get close, giving you reusable environment templates: Start with a clean computer from the `debian/13` image, with Hoody Kit enabled. Install Node.js, tools, and dependencies over the terminal URL. Add global npm packages (TypeScript, pnpm, yarn), configure Git, and prepare the development environment. Capture that state as a [snapshot](/foundation/computers/snapshots/#snapshot-creation) with a readable alias, `nodejs-dev-template-2025`. Omit `expiry` to keep it with no expiration date. Copy from the [template snapshot](/foundation/computers/copy-sync/#copy-from-a-specific-snapshot) into new projects. The tools are already installed, so there is no setup step. One template serves any number of computers. In the Hub, open **Computers**, pick the configured computer and open its **Backups** tab. Choose **Take snapshot**, enter a **Name** and press **Take snapshot**; **Delete after (days)** is optional. To start a new computer from it, choose **New computer from this** on the snapshot's row, then **Make the computer**. ## Advanced - **[CPU architectures](/foundation/computers/images/reference/#architectures):** an image's `architecture` field shows which CPU it targets. A computer from `debian/13` gets its server's architecture automatically, so there is nothing to match. - **[Image variants](/foundation/computers/images/reference/#variants):** an image's `variant` field names its configuration; for `debian/13` it is `default`. You still name the image by its alias. - **[Image icons](/api/computer-images/#get-apiv1imagesidicon):** download an image's icon with `GET /api/v1/images/{id}/icon`. An image without an icon returns a generic placeholder PNG. - **[Cost of an image](/foundation/computers/images/reference/#common-questions):** computers are not charged separately. A premium marketplace image has its listed purchase price. - **[Windows computers](/foundation/computers/images/reference/#base-image):** Every computer starts from `debian/13`. To run Windows inside a computer with KVM enabled, use [Hoody VM](/kit/vm/). ## Reference Fields, filters, architectures, ratings, Kubernetes setup, practices and troubleshooting: the [Computer Images reference](/foundation/computers/images/reference/). Every call and status: the [Computer Images API](/api/computer-images/). ## What's next - [Create, Edit, Delete](/foundation/computers/create-edit-delete/): use images in computer creation - [Snapshots](/foundation/computers/snapshots/): snapshot configured computers as templates - [Copy & Sync](/foundation/computers/copy-sync/): duplicate configured environments - [The Hoody Kit](/kit/): 20 HTTP services, on any image