Wednesday, 1 November 2023

XM Cloud :: Failed to register layer error

 While setting up my local instance for an XM Cloud project I got into a strange error while trying to build images locally, an error "failed to register layer: Cannot create layer with missing parent acf3d164746bcef47b6a7fd46c5912a1103931480f6bcf9336efa664f58ad669: The system cannot find the file specified." keep happening, in this post I will share the steps I tried to resolve the error, hopefully it will be useful for someone. 


Following is the full description of the error: 

failed to register layer: cannot create layer with missing parent acf3d164746bcef47b6a7fd46c5912a1103931480f6bcf9336efa664f58ad669: CreateFile C:\ProgramData\Docker\windowsfilter\acf3d164746bcef47b6a7fd46c5912a1103931480f6bcf9336efa664f58ad669: The system cannot find the file specified.
Waiting for CM to become available...
Invoke-RestMethod : Unable to connect to the remote server


If you search online for this error, you can find explanation like,  his error occurs because data for a layer already pulled and extracted (b30ce824...) was found to be missing when registering a layer based on it. The missing layer data was a windowsfilter subfolder with the same 64-character name. so what I should do to resolve, here are the steps I followed: 

  1. First of all I started with updating my docker desktop to the latest version, still with no luck...
  2. I did run the following command to clean my local data, docker image prune -a -f, still with no luck. 
  3. I did run the following command to clean my local data, docker system prune -a -f, still with no luck.
  4. I did clean %temp% folder content 
  5. restart docker desktop and services 
  6. still no luck....
The last disparate action I took was to purge data using docker desktop as you can see from the following screenshot: 


Once I did that, I ran the up.ps1 command and I was able to build images locally and start my XM Cloud instance: 

image

image


Hopefully this will be useful for someone and save you some time. 

No comments:

Post a Comment