Docker inside a computer

Docker and Compose are installed in the base image. Containers run inside your computer and share its disk, CPU, RAM and network policy; they are not separately billed CE computers.

Choose storage before creation

The initial disk is 40, 80, 160 or 320 GB for ac-2, ac-4, ac-8 or ac-16. Resize later changes CPU and RAM only. Images, build caches, volumes and logs all consume the original disk. Leave space for the filesystem and use application retention limits rather than filling it completely.

Run and expose a service

Upload a reviewed Compose definition, then use docker compose up -d inside the guest. Check docker compose ps and the application's health endpoint before issuing a CE preview for its listening port. A preview must target a service reachable inside the guest; binding only to an unrelated container-private interface is not enough. A small set of guest ports is reserved; using one returns 422.

Previews are private by default. Program clients need a program token; browser clients need a browser grant. Share links are separate credentials with bounded lifetime and uses. See Expose a web app. Outbound policy and SMTP restrictions still apply to container traffic.

Stop, save and recover

Memory pause saves the whole VM, including containers. A normal stop gives applications an opportunity to shut down and then powers off; a forced stop may interrupt writes. Application-consistent snapshots require the application's own flush/backup steps. Export important volumes outside the server. Nested virtualization and GPU access are not available.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.