No instance will start and just ends in docker error code 125

Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.

Screenshots of text are prohibited. Always copy and paste text as text.

Make sure you search before posting! Duplicate posts for the same issue may not be answered.

OS Name/Version: ubuntu 22.04.5 LTS

Product Name/Version: Amp Phobos v2.6.3.2, built 22/10/2025 11:11

Problem Description:

I get the following error in the code block for any game i try to create an instance of. Doesnt matter the game, just produces the error code 125 message and nothing is created.



Non-managed instances exist, autoconfigure cannot guarantee that the configuration is valid!

Unable to find image 'games:latest' locally
docker: Error response from daemon: pull access denied for games, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Run 'docker run --help' for more information
Failed to configure new instance Minecraft01 - Startup failure: Docker returned error code 125. Please check the AMP Logs for further info.
Configuration Failed: Startup failure: Docker returned error code 125. Please check the AMP Logs for further info.
Create Instance Failed: Startup failure: Docker returned error code 125. Please check the AMP Logs for further info.

Steps to reproduce:

  • installed amp and left it for 2 weeks then came back updated and bought and put license into the install

Actions taken to resolve so far:

  • Double checked docker permissions and group permissions.

  • other docker containers on the system are fine and running. shut down other containers that i though might have conflicted and still nothing. Tried searching google only to find that most others at least get an instance made before the error.

  • updated docker

  • restarted docker services.

  • logged out of docker hub and back in to make sure its using the right docker hub account

At this point i have a headache and not enough coffee, what did i miss or do wrong?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.