Docker sur Windows, sans Docker Desktop ni WSL.

Solon updates itself in one click, and still never behind your back. *Version française plus bas.* New - Install update from the app. When a new version exists (banner at the top, or Settings → Updates), *Install update* downloads the installer from github.com, checks its SHA-256 against the `SHA256SUMS.txt` published with the release, then Windows asks you to allow the install. The engine and running containers stop for about a minute; Solon reopens and starts them again. A file whose checksum does not match is deleted and never run. *Download* is still there to do it by hand. - Compose file checked before saving. The Compose tab now shows line numbers. YAML syntax is checked as you type; on Save, `docker compose config` checks the structure (unknown key, wrong type, undeclared network, missing env file…). The error appears with the faulty line marked in the gutter and a *Go to line* button; *Save anyway* stays available. Engine stopped: syntax only. Installation Download `Solon_0.1.13_x64-setup.exe` and check its SHA-256 against `SHA256SUMS.txt`. Installing over 0.1.x keeps your images, containers and volumes. If VS Code's Containers view stops refreshing after the update, run *Developer: Reload Window* once.

Solon now runs on Windows Home, and installs on a freshly installed Windows. *Version française plus bas.* New - Windows Home is supported. Home has no Hyper-V role and no `vmms` service, but it has the Virtual Machine Platform, and that is all Solon needs since file sharing moved to solonfs. The installer enables the platform and asks for one restart. Verified on Windows 11 Home 25H2: engine ready, `docker` working, Windows folders shared both ways, published ports and `*.solon.local` addresses. The legacy 9P file-sharing fallback is unavailable on Home; the default sharing works. Fixed - Fresh Windows: the service would not start. A freshly installed Windows has no `vcruntime140.dll`; Solon's service failed with "DLL not found" (0xC0000135) and the installer sat on an invisible error dialog. This affected any edition without the Visual C++ redistributable. All Solon executables now embed the C runtime and depend on nothing but Windows itself. Installation Download `Solon_0.1.12_x64-setup.exe` and check its SHA-256 against `SHA256SUMS.txt`. Installing over 0.1.x keeps your images, containers and volumes. The installer is not signed yet: in SmartScreen click *More info*, then *Run anyway*. If VS Code's Containers view stops refreshing after the update, run *Developer: Reload Window* once.

A simpler Projects page and an installer that looks like Solon. *Version française plus bas.* Changed - "Always start with Solon" is gone. The checkbox on each project card and the list in Settings are removed. Solon keeps doing the one thing that matters: what was running when it stopped is started again when it comes back ("Resume what was running", on by default). Existing settings files that still mention the old option are read without complaint. - The installer carries Solon's icon. `Solon_0.1.11_x64-setup.exe` shows the Solon hexagon in Explorer and in your browser's downloads instead of the generic installer icon, and the setup pages show the logo in the header and side panel. Installation Download `Solon_0.1.11_x64-setup.exe` and check its SHA-256 against `SHA256SUMS.txt`. Installing over 0.1.x keeps your images, containers and volumes. The installer is not signed yet: in SmartScreen click *More info*, then *Run anyway*. If VS Code's Containers view stops refreshing after the update, run *Developer: Reload Window* once.

VS Code Dev Containers works with Solon. *Version française plus bas.* Fixed - `docker exec -i` never saw the end of its input. Piping data into a container (`tar … | docker exec -i … tar -xf -`) hung forever: Solon's Docker pipe was in byte mode, where the Windows Docker client has no way to say "I am done writing". The pipe is now in message mode, like Docker Desktop's, and the container's output keeps flowing after the input ends. This is exactly how the VS Code Dev Containers extension installs its server inside a container. - VS Code's Containers view stopped refreshing on its own. The Containers extension listens to `docker events` once, at startup, and gives up for good after three immediate failures. Solon's Docker pipe only appeared once the machine was up, so a VS Code window opened while Solon was starting (at logon, or during an update) lost live refresh for the whole session and needed the Refresh button. The pipe now exists from the moment the Solon service starts; a `docker` command that arrives while the engine is still starting waits for it instead of failing. When Solon is stopped, `docker` gets a clear "Solon is stopped. Open the Solon app to start it." A window that already lost its listener re-arms it with *Developer: Reload Window*. - `docker` with the default context. The Dev Containers extension runs `docker` with `DOCKER_CONTEXT=default`; Solon's `docker` took that as a request for another engine and pointed at Docker Desktop's pipe. The default context now follows Solon, as Docker intends. With both fixes, Dev Containers open on Solon. New - Dev Containers documented: a `.devcontainer/devcontainer.json` folder opens in VS Code with "Reopen in Container" using Solon's `docker`; the workspace is mounted both ways, ports are forwarded, and the container shows up in Solon like any other. See the README. Installation Download `Solon_0.1.10_x64-setup.exe` and check its SHA-256 against `SHA256SUMS.txt`. Installing over 0.1.x keeps your images, containers and volumes. The installer is not signed yet: in SmartScreen click *More info*, then *Run anyway*.

Polish after a full walk through the app. *Version française plus bas.* Fixed - Sleeping services count as running. A service paused by Solon (wake on demand) showed the project as "1/2 running" with no address; it is reachable, so cards, addresses and counters now treat it as running. - Containers list: the "Asleep" pill no longer overflows its column. - Container page: long names stay on one line; the Inspect tab wraps its JSON instead of scrolling sideways. - Images: the registry mirror prefix is hidden; the short name is shown, the full one on hover. - Debug shell on a fresh engine: when the registry limited anonymous downloads, the toolbox build failed silently. Solon now prepares the base image itself, falls back to Docker Hub, and explains when it cannot. - Escape closes the stack gallery and the "Find projects" dialog; Ctrl+8 works from the terminals. Installation Download `Solon_0.1.9_x64-setup.exe` and check its SHA-256 against `SHA256SUMS.txt`. Installing over 0.1.x keeps your images, containers and volumes. The installer is not signed yet: in SmartScreen click *More info*, then *Run anyway*.