instabox 0.8.264 → 0.8.266
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 +1 -1
- package/skills/instabox/SKILL.md +1 -1
package/cli/SHA256SUMS
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
8d6eaaa6b6c9938859f6a0758b0cd9b90695b6a97b04ab6303f1243adfac20c7 instabox-darwin-amd64
|
|
2
|
+
f46eaa34f23971f1cf13db2c61d38d704ead923e59fc55b899b6d0d16dfe9632 instabox-darwin-arm64
|
|
3
|
+
36c0e5e8c30d56dcbfbead19b2ce8646676b7d79c125c0a501827491a0701c46 instabox-linux-amd64
|
|
4
|
+
0c26df1a2d4b88336700f3d984403ab08dd6ef8437b98efa821bb01b37edcae8 instabox-linux-arm64
|
|
5
|
+
e03e0303bad80ef3593e150ea93f0fcbc0cc5f339bbd258c05946ca6dfee5f24 instabox-windows-amd64.exe
|
|
6
|
+
8120ba0701a6d87c96aff5427f7c477e9066c8259cd76d0436388f9f0d53e3bd 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
package/skills/instabox/SKILL.md
CHANGED
|
@@ -93,7 +93,7 @@ instabox rm --yes work # delete the box (without --yes
|
|
|
93
93
|
- To find the boxes your session made, tag each with `create --meta session=ID` and list them with `instabox ls --meta session=ID [--json]` (repeat `--meta` to match several pairs, all must match). The server filters, within your own orgs only. Do not keep box IDs by hand or probe for 404s.
|
|
94
94
|
- `create --ready-timeout D` (1s-1h): if the box is not running D after the request, `create` tries to delete it and exits 6 with `create_timeout` within seconds (Ctrl-C while it waits does the same, exit 130). The server deletes a box only once its create has ended, so a create still running is left: the `--json` error then has `deleted: false` and `createRunning: true`, and `hint` gives the `instabox rm --yes` command to run once `instabox get` no longer shows it creating. `deleted` is `true` only once the delete is confirmed; `deletePending: true` (with `deleteOperationId`) means the delete was requested but not confirmed within 20 s, so check with `instabox get` and `rm` it if it is still there. Always check `deleted`; add `--delete-after` as a backstop. `machineId` names the box (absent only when the create request got no answer: check with `instabox get NAME`). It bounds only the create, not the box's life: a box ready in time runs as usual. The setup script and devcontainer are not counted. On exit 6, create again or try another size or template.
|
|
95
95
|
- Idle auto-pause defaults to 30 minutes. Paid boxes allow any whole minute from 5 to 30 (a part minute, below 5m or above 30m is refused, nothing created), or `0` to turn it off. Free boxes keep 30 minutes unless an admin grants an idle override; asking another value on a free box fails (`spec_not_allowed`, exit 5, nothing created), so leave `--auto-suspend` out there. Idle means no agent working, no terminal use and little CPU. `create --json` and `get --json` show the effective setting as `autoSuspendAfterSeconds` (`0`: off), and `readyAt` minus `createdAt` is the create time.
|
|
96
|
-
- Max run minutes is independent of idle activity: `-1` is unlimited, `0` pauses immediately, and a positive integer forces a pause after that many running minutes.
|
|
96
|
+
- Max run minutes is independent of idle activity: `-1` is unlimited, `0` pauses immediately, and a positive integer forces a pause after that many running minutes. On free boxes the service sets it and only an admin session can override it: each run starts at 120 minutes and grows with use up to 480. Use is commands, file access, port requests, terminal or SSH traffic and CPU load; activity leases and `wake` keep a box from an idle pause but do not grow its run. A box with no use near the end of its window pauses then, with the cooldown below. A paused or stopped free box reports 480, the most a run can last; the next run starts at 120 again. Paid boxes default to `-1` and can change it. Read the current `maxRunMinutes` and `runStartedAt` instead of assuming a fixed deadline. An idle override does not permit changes to a free box's runtime cap. The first limit reached pauses the box; both timers restart after sleep and wake.
|
|
97
97
|
- A runtime pause blocks every wake path during a server-configured cooldown, 5 to 20 minutes by default (`409 machine_cooldown` with `Retry-After`). On the free plan, back-to-back max-run pauses rest longer: 60 to 75 minutes for the 2nd in a row and 120 to 135 for later ones; the count starts over when a run ends with no cooldown owed (idle pause, a user pause or stop) or starts 2 hours or more after the last cooldown. A security lock (up to 24 h) is a cooldown too and keeps the count. Wait until the `cooldownUntil` deadline shown by `instabox get`; edits cannot clear it. Afterward, a box that paused itself (idle or runtime) wakes on `exec`, `ssh`, `files`, a public port request or `instabox wake <box>`. A box you paused (`instabox suspend`) or stopped does not wake on any of these, `wake` included: run `instabox resume <box>` or `instabox start <box>`. A zero runtime cap must be changed before waking. A normal pause preserves memory and processes. `ps`, file writes and taking an activity lease wake it too; `get`, `ls`, `logs` and exec history never do. Full list: https://instabox.sh/docs/machines/auto-pause#what-wakes-a-machine
|
|
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
|