Docker container creation instance process

Questions
,
18

Ah, classic JSON meltdown! That error is AMP basically tripping over itself while reading an instance config file. Most likely, the configuration or metadata for that instance got corrupted somewhere along the line.

Here’s the move:

  1. Check your AMP install version.
    It looks like the system is running AMP v2.5.0.12 while your instance logs say AMP 2.6.0.12. That mismatch will absolutely cause chaos. Update AMP Instance Manager first to 2.6.0.x to match your instances.

    • To update AMP on Windows:
      • Download the latest installer from the CubeCoders website.
      • Run it, ensuring it updates your AMP Instance Manager properly.

  2. After updating:
    Try reactivating the instance again with ampinstmgr reactivate <InstanceName>.

  3. If the issue persists even after syncing versions:
    It might require rebuilding the instance metadata manually, but let’s cross that bridge if we have to. Let me know how the update goes first! :rocket:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback