Hi… This seems to be the culprit. My own PG instance has a v0.0.62
there, and the source code surrounding that particular message specifically is checking the ImageVersion
:
// Validate image version to ensure it's compatible with this feature.
if machine.ImageVersion() == "" || machine.ImageVersion() == "unknown" {
return fmt.Errorf("command is not compatible with this image")
}
This glitch seems to crop up occasionally, maybe in connection with lower-level Machine problems. Was it recently migrated, by any chance? (You can check with fly m status
, in the INFO
column.)
[Also, if you do have Support for the corresponding organization, I think this would qualify, .]
Hope this helps a little!