Play with Docker
play-with-docker.com · Compute · 1 record · JSON
Play with Docker Compute
deadanonymousno cardDretention-clamped
| Free tier | no longer available: Play with Docker is unavailable starting 2026-03-01 unit none; metered on wall-clock; this was the canonical anonymous free VM in every list older than 2026-03 |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | the service is withdrawn |
| Egress | not applicable |
| Identity | anonymous was anonymous; the service is withdrawn |
| Limits |
a 4-hour session was the historical limit |
| Binding | retention-clamped the service is unavailable from 2026-03-01, so the withdrawal is the end of it |
| Interface | ssh was a browser terminal with Docker-in-Docker |
| Tooling | was docker and docker compose in a browser tab |
| Composes with | none: withdrawn |
| Reliability | no reliability event recorded |
| Notes | The deprecation notice is on the playground host, not on docs.docker.com, and the Markdown rendering of the playground page drops it: the page still returns 200 with the playground description. Reading the status code or the rendered text finds a live product. The raw HTML carries the notice. |
| Evidence rung | documented |
| Checked | 2026-10-22 (live); stale on 2026-11-21 |
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | labs.play-with-docker.com/ | 'Deprecation notice: Play with Docker will be unavailable starting March 1, 2026', read from the raw HTML. The Markdown extraction of the same page drops the notice and returns only the playground description |
| 2026-10-22 | docs.docker.com/ | no match for 'Play with Docker' or 'unavailable' |
More fields (8)
{
"shape": null,
"billing_model": "flat-pool",
"session_cap": null,
"keep_rate": null,
"persistent_storage": null,
"network_out": null,
"free_tier_kind": "none",
"census_rows": [
"play-with-docker"
]
}Unknown or withheld values (3)
$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed