Known issues
This page records behavior that needs care or a verified release. A code fix under review is not a guarantee about a running service.
Sandbox pause and expiration
Create a sandbox, run commands, then call kill. connect attaches to an existing sandbox without changing its state, so it does not resume a paused or stopped sandbox. Pause, resume, snapshot, and restore are available; see Pause, resume, and snapshots. Fork and file watching return HTTP 501. lizard sandbox ssh opens an interactive shell with your CLI credentials. SSH protocol access is not available, so SSH clients, scp, and port forwarding do not work.
Pausing closes open network connections. If the processes cannot be saved, the sandbox keeps running and reports the reason in pauseError. A paused sandbox resumes only on its own node; if that node fails, the paused state is lost.
Files and running processes remain available while the sandbox runs. After it stops, only files written to an attached Persistent Volume at /workspace can be reused by a later sandbox. Without a volume, /workspace is temporary. Each volume attaches to one sandbox at a time and uses node-local storage; export files that must survive node loss.
Redeploy is not rollback
lizard redeploy builds the selected source again with the current configuration. It does not select a previous build. A failed build and a failed start have different effects; inspect the active service and its logs before choosing a recovery step. Do not assume every runtime keeps the old release serving through a failed start.
Dockerfile precedence
Explicit build or start commands take priority over a repository Dockerfile. Clear those overrides when selecting dockerfilePath. A settings update can itself start a build, so check events before sending another redeploy. See Dockerfile troubleshooting.
Templates and MCP
Choose a template from the current catalog. Enabled templates include base, codex, and interpreter; availability depends on the region and pool capacity. interpreter includes Python and common data libraries. Check tool versions inside your sandbox. The public CLI does not provide a custom-template upload flow.
Lizard Skill uses Lizard CLI. That workflow does not expose an MCP transport. Hosting your own remote MCP server is a separate application deployment; see the guide.
Service port changes: fixed and verified on 2026-09-09
The September 7 check found HTTP 503 after changing an upload service from port 3000 to 80, despite a ready process. The production fix now applies the chosen port to the running service and preserves an explicit port during upload and rebuild. A live port-change check passed on September 9. Check the public URL after a deployment as well as the service state.
Upload archives and failed-build exit codes: fixed
Lizard CLI 0.3.95 excludes macOS ._* metadata entries from source uploads and returns a nonzero exit code for failed cloud builds. Update older CLI versions; COPYFILE_DISABLE is no longer needed. The framework checks cover uploads from macOS with the current CLI.
A successful build alone does not prove the app works. Check the public URL, routes, forms, and data operations after deployment.
Updated