Patch shipped: v1.6.685 — A clear message when Docker's own disk has gone read-only during an update
Posted by Chris
These SparkBox updates are now available: v1.6.685 — A clear message when Docker's own disk has gone read-only during an update - If the disk holding Docker on your box had gone read-only (usually after a disk error or a full disk), the one-click update stopped with a raw Docker error — "Update helper exited with code 125: mkdir …: read-only file system" — and left you guessing. The update now says what happened in plain words: which folder Docker could not create, that the disk holding it is read-only, and that the fix is to check that disk and reboot before updating again. Nothing on the box is changed, and it no longer retries something that could not succeed. Update from the SparkBox dashboard, or run sudo sparkbox upgrade on your SparkBox host. If a problem remains after updating, submit a private support ticket or reply here. Include your SparkBox version and what you see; leave passwords and licence keys out.