Creating (and starting) an instance on mounted Datastore fails

Technical Support
5

Alright, if the amp user can write there directly, we know there’s something more interesting at play :eyes:.

Since it seems docker is being used here, let’s check if your mounted datastore has the right docker permissions set. Docker often has issues with mounted directories due to its strict volume permissions when running containers. The clue is in the logs you provided (“creating instance fails during docker operations”).

Try the following:

  1. Make sure your mounted directory has the necessary SELinux contexts (though SELinux is usually off on Ubuntu, let’s just rule it out):

    sudo chcon -Rt svirt_sandbox_file_t /mnt/amp/instances

  2. Add the :z option to your docker volume mounts in AMP—this tells Docker to adjust mount permissions automatically. For example:

    -v "/mnt/amp/instances/mcLV01:/AMP:z"

    You’ll need to check if that’s happening within AMP’s docker run configurations through its interface under Configuration -> Datastore.

  3. Restart the instance creation process after applying these settings.

Let me know how that pans out for you. :sweat_smile:

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