Meta tags:
description=Namespace accelerates the development workflow of fast-moving software engineering teams. Best-in-class compute and development-supporting services that lead to 2x-10x faster builds, tests, and more.;

Headings (most frequently used words):

image, images, an, custom, dockerfile, building, optimization, creating, devbox, from, your, managing, next, steps, introducing, devboxes, we, re, hiring, join, us, why, dockerfiles, listing, updating, expiring,

Text of the page (most frequently used words):
nsc (73), image (31), the (24), #devbox (21), github (17), your (15), and (14), devboxes (13), images (13), build (12), list (10), team (9), base (9), registry (9), artifact (9), docker (9), create (8), setup (8), actions (8), from (7), custom (7), you (7), namespace (7), cache (7), profile (7), namespacelabs (7), golang (6), name (6), with (6), use (6), dockerfile (6), install (6), describe (6), action (6), nscloud (6), overview (6), remote (5), development (5), version (5), all (5), container (5), run (5), for (5), context (5), upload (5), tools (5), started (5), token (5), sessions (4), that (4), machine (4), workspace (4), dashboard (4), checkout (4), cli (4), this (4), any (4), git (4), path (4), get (4), update (4), login (4), vault (4), buildx (4), instance (4), managing (3), via (3), ssh (3), created (3), expire (3), new (3), using (3), check (3), optimization (3), status (3), size (3), into (3), need (3), dev (3), default (3), user (3), set (3), env (3), everything (3), apt (3), getting (3), auth (3), download (3), ingress (3), expose (3), kubernetes (3), terminal (2), code (2), existing (2), were (2), are (2), same (2), repository (2), can (2), start (2), builders (2), add (2), directory (2), share (2), environment (2), dockerfiles (2), gopath (2), bin (2), usr (2), local (2), tar (2), curl (2), linux (2), needs (2), etc (2), sudoers (2), sudo (2), runtimes (2), dependencies (2), guide (2), installed (2), pre (2), trust (2), generate (2), delete (2), sccache (2), pants (2), gradle (2), bazel (2), expiration (2), extend (2), volume (2), job (2), access (2), logs (2), usage (2), builds (2), circleci (2), security (2), limits (2), storage (2), logo (2), open (2), last, updated, june, 2026, persistent, survive, disconnections, restarts, lifecycle, operations, sizes, defaults, monitoring, connect, cursor, zed, jetbrains, next, steps, not, affected, prevent, expiring, rebuild, publish, will, latest, continue, they, updating, visit, browse, view, details, listing, click, select, picker, choose, optionally, provide, clone, com, myorg, myrepo, once, built, creating, runs, automatically, typically, takes, few, minutes, track, its, progress, output, after, completes, converts, optimized, disk, format, what, allows, boot, seconds, rather, than, pulling, unpacking, every, additional, options, sent, contains, files, don, keep, small, dockerignore, point, different, location, useful, monorepo, where, lives, subdirectory, but, full, repo, required, descriptive, like, published, available, immediately, frontend, node20, argument, looks, building, consistent, environments, across, entire, portability, software, configure, customize, settings, flexibility, definition, alongside, control, syntax, already, know, familiarity, provides, why, home, fssl, https, go1, amd64, example, boilerplate, below, yours, customise, above, line, chmod, 0440, nopasswd, echo, uid, 1001, adduser, disabled, password, gecos, non, root, passwordless, var, lib, lists, essential, certificates, debian_frontend, noninteractive, common, ubuntu, standard, define, workflow, assumes, have, authenticated, haven, yet, see, most, teams, managed, when, specific, toolchains, system, packages, configuration, baked, package, language, support, center, soc2, changelog, revoke, relationships, policy, url, release, submodules, test, optimize, cleanup, attach, kubectl, kubeconfig, write, port, forward, proxy, rdp, vnc, top, report, destroy, installation, turbocache, breakpoint, cluster, api, sdk, explorer, rwx, openid, gcp, aws, federation, permissions, audit, logging, data, residency, billing, workspaces, egress, filtering, performance, networking, secrets, volumes, resource, shapes, display, observability, windows, macos, compute, framework, tailscale, claude, checkouts, nix, moonrepo, android, emulators, playwright, turborepo, integrations, coding, agents, introduction, containers, previews, tracing, reference, optimizing, migration, debugging, caching, roles, hiring, join, read, article, introducing, sidebar, company, resources, pricing, customers, cases,

Text of the page (random words):
custom images devboxes namespace logo use cases customers pricing resources company get started login open sidebar introducing devboxes read article we re hiring join us open roles logo overview github actions getting started caching docker builds custom base images debugging github actions migration guide optimizing usage reference docker builders getting started container registry tracing logs previews containers kubernetes devboxes introduction managing devboxes remote development sessions custom images coding agents integrations bazel turborepo playwright android emulators gradle sccache circleci pants moonrepo nix git checkouts docker images claude tailscale any framework compute overview linux macos windows observability ssh remote display machine shapes resource limits storage overview cache volumes container registry artifact storage secrets networking overview ingress performance security egress filtering workspaces overview access billing and limits data residency security audit logging permissions federation overview aws gcp openid github actions circleci rwx dashboard github actions builds registry usage explorer api sdk github actions namespacelabs nscloud setup namespacelabs nscloud setup buildx action namespacelabs nscloud cluster action namespacelabs nscloud cache action namespacelabs nscloud checkout action namespacelabs nscloud expose kubernetes action namespace actions upload artifact namespace actions download artifact namespacelabs breakpoint action namespace actions setup turbocache cli installation nsc version nsc login nsc workspace describe nsc create nsc destroy nsc extend nsc list nsc instance report nsc logs nsc top nsc ssh nsc vnc nsc rdp nsc proxy nsc instance port forward nsc instance download nsc instance upload nsc kubeconfig write nsc kubectl nsc docker login nsc docker attach context nsc docker remote nsc docker buildx setup nsc docker buildx cleanup nsc docker buildx status nsc build nsc base image upload nsc base image optimize nsc run nsc expose container nsc expose kubernetes nsc ingress list nsc ingress generate access token nsc github profile nsc github profile create nsc github profile list nsc github profile describe nsc github profile update nsc github profile delete nsc github profile test build base image nsc github base image list nsc github base image describe nsc github job list nsc github job describe nsc git checkout update submodules nsc volume list nsc volume release nsc artifact upload nsc artifact download nsc artifact expire nsc artifact extend nsc artifact describe nsc artifact cache url nsc registry list nsc registry describe nsc registry share nsc registry update image expiration nsc registry policy nsc registry default expiration nsc cache bazel setup nsc cache gradle setup nsc cache pants setup nsc cache sccache setup nsc vault list nsc vault add nsc vault set nsc vault delete nsc auth check login nsc auth generate dev token nsc auth trust relationships nsc token create nsc token list nsc token revoke changelog trust center soc2 status support custom images pre package your development tools language runtimes and dependencies into a custom base image devboxes created from your image start with everything pre installed most teams can get started with namespace s managed base images custom images are for when you need specific toolchains system packages or configuration baked in this guide assumes you have the devbox cli installed and authenticated if you haven t set that up yet see getting started dockerfile use a standard dockerfile to define your development environment install the tools runtimes and dependencies your workflow needs from ubuntu 24 04 install common development tools run apt get update debian_frontend noninteractive apt get install y sudo git curl build essential ca certificates rm rf var lib apt lists create a non root user with passwordless sudo run adduser disabled password gecos uid 1001 devbox echo devbox all all all nopasswd all etc sudoers d devbox chmod 0440 etc sudoers d devbox install the tools your team needs everything above this line is boilerplate everything below is yours to customise example install go run curl fssl https go dev dl go1 26 0 linux amd64 tar gz tar c usr local xz env path usr local go bin path env gopath home devbox go env path gopath bin path set the default user for terminal sessions user devbox why dockerfiles using dockerfiles for base images provides familiarity use the same syntax you already know version control check your environment definition into git alongside your code flexibility install any software configure any tools customize any settings portability share consistent environments across your entire team building an image the argument to devbox image build is the build context directory by default it looks for a dockerfile in that directory devbox image build my image name my team golang name is required use a descriptive name like my team golang or frontend node20 the image is published to your workspace and available immediately use f to point to a dockerfile in a different location this is useful in a monorepo where the dockerfile lives in a subdirectory but you need the full repo as context devbox image build name my team dev f devbox dockerfile the build context is sent to namespace s remote builders if your context contains files you don t need in the build add a dockerignore to keep the upload small run devbox image build h for additional options optimization after a build completes namespace converts the container image into an optimized disk format this is what allows devboxes to boot in seconds rather than pulling and unpacking a container image on every start optimization runs automatically and typically takes a few minutes you can track its progress in the cli output and in the images dashboard creating a devbox from your image once your image is built create devboxes from it via the cli devbox create image my team golang or with a repository checkout and machine size devbox create image my team golang checkout github com myorg myrepo size m via the dashboard go to devboxes and click create devbox select your custom image from the image picker choose a machine size and optionally provide a repository to clone managing images listing images devbox image list or visit the images dashboard to browse all images in your workspace view details and check optimization status updating an image rebuild with the same name to publish a new version new devboxes will use the latest version existing devboxes continue using the version they were created with devbox image build my image name my team golang expiring an image expire an image to prevent new devboxes from using it devbox image expire my team golang existing devboxes that were created from the image are not affected next steps remote development connect to your devbox via ssh vs code cursor zed or jetbrains managing devboxes lifecycle operations machine sizes workspace defaults and monitoring sessions persistent terminal sessions that survive disconnections and devbox restarts last updated june 9 2026