Different Postgres images in same cluster

In a Postgres app with 3 machines, all machines don’t have the exact same image. Two have “flyio/postgres-flex:18 (v0.2.0)” and the other has “flyio/postgres-flex:18 (v0.2.0**-pre-1**)”.

This brings the "Your app is currently running multiple images." warning message the app’s dahsboard.

Trying to force the image on a machine like this…:

fly m update <my_machine_id> -a <my_app_name> -i ‘flyio/postgres-flex:18 (v0.2.0-pre-1)’

Results in this error:

Error: failed to run query ($appName: String!, $imageRef: String!) { app(name: $appName) { id image(ref: $imageRef) { id digest ref compressedSize: compressedSizeFull manifest } } }: couldn’t parse image ref: “flyio/postgres-flex:18 (v0.2.0-pre-1)”

“fly image show -a <my_app_name>” gives the same kind of error:

unable to fetch latest image details for flyio/postgres-flex:18: failed to run query($image: String!, $flyVersion: String) { latestImageDetails(image: $image, flyVersion: $flyVersion) { registry repository tag version digest } }: “Unable to resolve latest upgradeable tag for flyio/postgres-flex:18.”

Why aren’t all machines with the same image anyway to start with? How can I update the image to set them all on par?

Hi Paul, ‘flyio/postgres-flex:18 (v0.2.0-pre-1)’ is not a valid image identifier. Try just flyio/postgres-flex:18.