instabox 0.8.304 → 0.8.306
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/cli/SHA256SUMS +6 -6
- package/cli/instabox-darwin-amd64 +0 -0
- package/cli/instabox-darwin-arm64 +0 -0
- package/cli/instabox-linux-amd64 +0 -0
- package/cli/instabox-linux-arm64 +0 -0
- package/cli/instabox-windows-amd64.exe +0 -0
- package/cli/instabox-windows-arm64.exe +0 -0
- package/package.json +2 -2
- package/skills/instabox/SKILL.md +2 -0
package/cli/SHA256SUMS
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
659c5b05d3e794e057283239cf61f8f0a45f08d4d31dbc6709979450d0a3bd08 instabox-darwin-amd64
|
|
2
|
+
99798d8ed899f2435fd2dbc132e2bd3c0bd117863e98533581919642a4cbcab2 instabox-darwin-arm64
|
|
3
|
+
87604bf2e48f18fa3b4f0dde662f0c19d00812ef3c23b631819836f620b156da instabox-linux-amd64
|
|
4
|
+
ec05393b91926fb97d93a8d525da412cd5e379d6ff95f6e3153f652d52c7ea3a instabox-linux-arm64
|
|
5
|
+
fc90f9816310d8ee81459131282628e5dcc36895e290c6cffa42f9c310dc4190 instabox-windows-amd64.exe
|
|
6
|
+
30121575dfdc05f354fb3951f8816f379dacf8b25cddec16d827c2f7cd94f73d instabox-windows-arm64.exe
|
|
Binary file
|
|
Binary file
|
package/cli/instabox-linux-amd64
CHANGED
|
Binary file
|
package/cli/instabox-linux-arm64
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "instabox",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.306",
|
|
4
4
|
"description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -31,5 +31,5 @@
|
|
|
31
31
|
"devDependencies": {
|
|
32
32
|
"prettier": "3.9.9"
|
|
33
33
|
},
|
|
34
|
-
"gitHead": "
|
|
34
|
+
"gitHead": "fba37c58fca7322d9a62c3f85f2a1f147038fcea"
|
|
35
35
|
}
|
package/skills/instabox/SKILL.md
CHANGED
|
@@ -98,6 +98,7 @@ instabox rm --yes work # delete the box (without --yes
|
|
|
98
98
|
- Kernel updates (a patched guest kernel, e.g. CVE-2026-98432, fixed in 6.18.60): a box runs the new kernel from its next cold boot, files kept. Running box: `instabox restart <box>` (or `instabox stop <box> && instabox start <box>`). Stopped box: `instabox start <box>`. Paused box (suspend or idle auto-pause): `instabox resume <box> && instabox restart <box>`; a paused box refuses `stop` and `restart`, and `start` resumes it with the old kernel in memory. A `sudo reboot` inside a box that comes back by itself is a cold boot too. Resume alone is not. New boxes start on the new kernel, and so do boxes from a snapshot of a box whose template does not pin its kernel. Check with `uname -r` (`6.18.60-instabox`). Templates with a pinned kernel: `android` (`-instabox-android`) and `omarchy` (restricted access, `-instabox-drm`). Their boxes keep the kernel they were created with through all of the above, and boxes from their snapshots or forks keep it too. Create a new box from the template and copy your files across (`instabox pull`, then `push`). A kernel package installed inside the box changes nothing.
|
|
99
99
|
- `sudo reboot` (or `reboot -f`) inside a box boots it again by itself, in about 20 seconds: same disks, processes and `/tmp` gone. `instabox get` lags by up to 30 seconds, so `running` does not mean it is back: retry the next `exec` while it fails with `retryable: true` (`503 host_unavailable`, or `409` "machine is restarting"), and compare `cat /proc/sys/kernel/random/boot_id` to know it rebooted. Do not `start` or `restart` it meanwhile: `restart` on it does nothing and exits 75, and that 75 does not mean run `restart` again (once the box is back it would power-cycle it). `sudo poweroff`, `halt` or `shutdown -h` inside stops it until `instabox start`. Boxes from older template versions stop on `sudo reboot` too: start them. https://instabox.sh/docs/machines/lifecycle#reboot-or-shut-down-from-inside-the-machine
|
|
100
100
|
- `instabox get`/`ls` showing `Running (host unreachable since ...)` (`--json`: `runtime.hostUnreachable: true`, `runtime.ready: false`, `runtime.hostLastSeenAt`) means the server the box runs on is not answering: exec, files and SSH fail with `503 host_unavailable`, and `start`/`resume` exit 75 instead of reporting success. Nothing to do on the box: retry later; it clears once the host answers again.
|
|
101
|
+
- A box that shows `running` with no `host unreachable`, yet keeps failing exec, files, SSH and the dashboard's Terminal with `503 host_unavailable` while `runtime.ready` stays `false` (exec and the Terminal say "this box's SSH server refuses instabox's key"; other paths, and older servers, say "machine unreachable"), usually has a sshd that refuses instabox's key after a change inside the box: a group- or world-writable `/`, `/etc`, `/etc/ssh`, `/etc/instabox` or `/usr` (a `chmod -R 775` or `chmod 777` there), the box user renamed, deleted or given another UID, or an edited `/etc/ssh` config. Retrying does not help. `instabox stop <box> && instabox start <box>` (a cold boot) usually puts those directory permissions back (a box that comes back on another host gets them at its next cold boot, so stop and start it once more); running processes are lost. A renamed user or an edited sshd config survives it: ask the person what changed inside the box.
|
|
101
102
|
- If `exec`/`ssh` stop answering (hang or time out on a running box), run `instabox restart <box>` (alias `recover`; `--timeout 20s` shortens the wait, `--json` prints the box). It stops the box, killing the VM if it has not shut down by the timeout (60 seconds by default), then starts it and waits until it runs. Files on the root disk and `/data` stay; processes do not, so start your servers again. A paused box is not hung: resume it. A box stuck in `starting` with no start in progress cannot be restarted; restart says so.
|
|
102
103
|
- Disk full (`df -h /data`)? Grow it with `instabox resize <box> --disk N` (`/data`, where HOME is), in GB. A running box grows online, no restart. A shrink, a paused box, or an image that can't grow online needs `--restart` (it stops the box, resizes the disk and starts it again; files stay, processes do not), else resize changes nothing and says so. A shrink must fit your data plus 10% (at least 1 GB), else it's refused (`disk_too_small`) and nothing changes. Free-plan boxes keep their size. The system disk (`/`) is the template's; you can't grow it.
|
|
103
104
|
- Need more CPU or memory? A paid box moves to another of its plan's sizes with `instabox resize <box> --vcpus N --mem-mib M` (Pro: 2/4096, 4/8192, 8/16384; Builder: 2/4096 up to 16/32768; Team: 2/4096 up to 32/65536), while it is stopped; add `--restart` on a running box, and run that from outside the box (from inside, the stop would end the command before the start, so resize refuses it; the same goes for a shrink with `--restart`). A size the plan does not have is refused before anything stops. The new size applies at the next start; free-plan boxes keep theirs.
|
|
@@ -236,6 +237,7 @@ What the CLI scrubs on its own, as a last line of defense and never as the reaso
|
|
|
236
237
|
|
|
237
238
|
## Habits
|
|
238
239
|
|
|
240
|
+
- Inside a box, keep instabox's way in working: do not loosen permissions on `/`, `/etc`, `/etc/ssh`, `/etc/instabox` or `/usr` (`chmod -R`, `chown -R`), rename, delete or renumber the box user, or edit `/etc/ssh`; any of them locks everyone out of SSH, exec and the Terminal. For npm `EACCES` on a global install, use `npm config set prefix ~/.npm-global` instead of changing `/usr/local`.
|
|
239
241
|
- Forgotten boxes pause themselves after 30 idle minutes. Delete a box with `instabox rm --yes NAME` once its work is done. `rm`, `snapshot rm`, `secrets rm`, `vault rm`, `keys rm` and `webhooks rm` ask y/N first and, off a terminal with no answer, delete nothing and fail, so pass `--yes` (`-y`).
|
|
240
242
|
- When the user asks for a new box, create one, with a name `instabox ls` does not already show. Offer an existing box only when they want to continue earlier work in it.
|
|
241
243
|
- `instabox usage` shows storage use and limits, this month's cost in USD and the credit balance (`--json`: `.cost.costUSD`, `.cost.creditsUSD`). It and `whoami` describe your personal org; a workspace has its own plan and limits: `instabox usage --org <workspace>` (whoami lists your workspaces and tiers). A quota error means delete or stop something; do not retry the same create in a loop.
|