AIDC Launch problems and fixes

Keep the failing command, the workspace, and the exact message together. Remove passwords, personal paths and private values before you share logs. After a fix, repeat the command that failed and check its result. Save any data you need before a rebuild, a delete or a reinstall.

aidcx doctor finds no reachable container engine: it is not installed, not running, or on macOS the managed virtual machine is stopped.

Then run the command you needed again.

The steps for your own account can finish while a step needing administrator rights did not. Ask whoever administers the computer to run the system half from a session where they can use administrator rights:

Do not put sudo in front of your own aidcx command. Then run aidcx doctor again.

Preparing the WSL2 distribution needs an interactive Windows desktop. Over SSH or from a scheduled task it fails with a message that looks like a permissions problem. Sign in through the desktop or remote desktop as the same user and run aidcx --install again; finished steps are skipped.

Keep the exact alert and the blocked file. Ask whoever manages security on that computer to verify where the file came from under your organization's rules before allowing it. Do not turn protection off. After it is allowed, run aidcx --install again and check the result.

Starting a workspace needs your MAIT sign-in:

If AIDC Launch prints an address for your account, open it, then run aidcx login --check. Never share your sign-in code.

Check the display part of the report, then the display connection on Linux:

If the project has the display turned off, turn it on with aidcx scaffold --x11 on, or aidcx start --x11 on for one start, and recreate the workspace with aidcx start --rebuild. Save data kept only inside the workspace first. On macOS, graphical apps appear through the managed virtual machine's display: use aidcx start --x11 on --gpu on.

aidcx doctor reports the secure runtime on its own line. If it is not installed yet, run aidcx --install. For a project that needs that isolation, use a computer that runs it; --runtime host uses the plain runtime instead.

The definition can name a folder or device that is missing on your computer. Correct the path if you need it. Otherwise let AIDC Launch comment the broken lines out, with a backup, or stop instead:

Check the change and the backup before you start again.

Two workspaces want the same port. Choose how to separate them:

aidcx list shows the ports each workspace uses.

Run uninstall as yourself, not with sudo. Preview with aidcx --uninstall, save any data you need, then run aidcx --uninstall --force. Uninstall lists the remaining system parts with the command to remove each.