After updating Laravel Vapor to use a custom Docker container I get the following error message during a vapor deploy:

==> Ensuring Functions Exist

     Deployment Failed 

AWS: The image manifest or layer media type for the source image 436312990568.dkr.ecr.eu-west-2.amazonaws/patient-portal:595c0e7e-44d3-4cba-ae29-40aac14ca0e5 is not supported.

I had created a Dockerfile for my environment as follow:

FROM laravelphp/vapor:php83-arm

COPY . /var/task

and updated the vapor.yml to include runtime docker-arm

adamsportal:
        memory: 1024
        storage: adamsportal-storage
        cli-memory: 512
        domain: adamsportal.theowldev.co.uk
        database: nest-db-test2
        network: nest2-test-network
        runtime: docker-arm
        build:
            - "COMPOSER_MIRROR_PATH_REPOS=1 composer install --no-dev"
            - "php artisan event:cache"
            - "npm ci && npm run build && rm -rf node_modules"

I can see that it successfully uploads to ECR and when I inspect the manifest it is like so:

{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 4663,
         "digest": "sha256:942a74e943c5d3eb617d58947806beb9a9371b8b016b2e1150f1c317ac04cbe9",
         "platform": {
            "architecture": "arm64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 566,
         "digest": "sha256:1340c45ef59e13199ae781ccf573eb02d6280ae564134144e0b2cfac60e2874e",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         }
      }
   ]
}

Though after vapor has uploaded the Assets I get the "Deployment Failed" error

I'm using: Laravel Vapor 1.65.1, Docker Desktop 4.38.0 (181591), On a Mac Pro M2 PRO

Anyone else had this issue?

After updating Laravel Vapor to use a custom Docker container I get the following error message during a vapor deploy:

==> Ensuring Functions Exist

     Deployment Failed 

AWS: The image manifest or layer media type for the source image 436312990568.dkr.ecr.eu-west-2.amazonaws/patient-portal:595c0e7e-44d3-4cba-ae29-40aac14ca0e5 is not supported.

I had created a Dockerfile for my environment as follow:

FROM laravelphp/vapor:php83-arm

COPY . /var/task

and updated the vapor.yml to include runtime docker-arm

adamsportal:
        memory: 1024
        storage: adamsportal-storage
        cli-memory: 512
        domain: adamsportal.theowldev.co.uk
        database: nest-db-test2
        network: nest2-test-network
        runtime: docker-arm
        build:
            - "COMPOSER_MIRROR_PATH_REPOS=1 composer install --no-dev"
            - "php artisan event:cache"
            - "npm ci && npm run build && rm -rf node_modules"

I can see that it successfully uploads to ECR and when I inspect the manifest it is like so:

{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 4663,
         "digest": "sha256:942a74e943c5d3eb617d58947806beb9a9371b8b016b2e1150f1c317ac04cbe9",
         "platform": {
            "architecture": "arm64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "size": 566,
         "digest": "sha256:1340c45ef59e13199ae781ccf573eb02d6280ae564134144e0b2cfac60e2874e",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         }
      }
   ]
}

Though after vapor has uploaded the Assets I get the "Deployment Failed" error

I'm using: Laravel Vapor 1.65.1, Docker Desktop 4.38.0 (181591), On a Mac Pro M2 PRO

Anyone else had this issue?

• docker
• aws-lambda
• laravel-vapor

1 Answer 1

My issue was solved by the Laravel Vapor support team:

Check your Docker Desktop settings in the General Tab and see if the “Use container for pulling and storing images” option is enabled?

If it is enabled, please disable it and then try deploying again.