https://medplum.com logo
Join Discord
Powered by
CannotPullContainerError: pull image manifest has ...
# support
y
CannotPullContainerError: pull image manifest has been retried 7 time(s): failed to resolve ref docker.io/medplum/medplum-server:5.0.11: docker.io/medplum/medplum-server:5.0.11: not found seems like there is a potential issue with 5.0.11 image?
@rahul1 this version is needed for the DB migration from what i am seing in -> https://github.com/medplum/medplum/blob/main/packages/server/src/migrations/data/data-version-manifest.json
a
Howdy! we had an issue on our end with the 5.0.11 image deployment. I would recommend switching to 5.0.12 or latest with these commands
y
thanks I will try that I went to 5.0.13 but was not able to perform migration
a
docker pull medplum/medplum-server:5.0.12 docker pull medplum/medplum-server:latest
y
Copy code
{
  "level": "INFO",
  "timestamp": "2026-02-03T19:06:51.086Z",
  "msg": "Post-deploy migration v32 delayed since the server cluster is not compatible",
  "queueName": "PostDeployMigrationQueue",
  "jobId": "56",
  "delayMs": 60000
}
after going to 5.0.13
from 
5.0.3
a
Do you have any information on why the cluster isn't compatible?
y
i think that would be because in the manifest we would need to migrate to ->
Copy code
"v32": {
    "serverVersion": "5.0.11"
  }
I downgraded to 5.10 and back to 5.13 and it seems to have fixed it
...but a bit nervous to replicate that process in production
a
5.0.3 to 5.0.13 are you getting any specific errors?
y
from what i have seen only had this warning ->
Copy code
{
  "level": "INFO",
  "timestamp": "2026-02-03T19:06:51.086Z",
  "msg": "Post-deploy migration v32 delayed since the server cluster is not compatible",
  "queueName": "PostDeployMigrationQueue",
  "jobId": "56",
  "delayMs": 60000
}
then went back to 5.0.10 did 
reconcile schema drift
in super admin and it migrated to v32, then went back to 5.0.13 and all seems good
will 5.0.1 image be deployed at one point? that would be ideal I think to go from 5.0.3 -> 5.0.11 (recommended version for migration to v32)-> 5.0.13
a
So could we go to 5.0.3 -> 5.0.10 -> 5.0.13?
y
had to do 
5.0.3 -> 5.0.10 -> 5.0.13 (migration not happening and giving warning)-> 5.0.10(migration worked to 32) -> 5.0.13
a
glad it worked, but very odd...
34 Views
PreviousNext
Powered by