This message was deleted.

In a quick glance it looks like the OPAL client process doesn't have file access to the backup file, you should chmod/chown it for the OPAL process user created in the dockerfile

I have manage to use chown and chmod to change the owner and permission of the file. As you can see from the first screenshot the opa.json is now owned by 'opal' user with all access permission (same as the autogenerated opa.json.tmp file) and I restarted the opal client. But it still thrown the same exception as show in the second screenshot

cc @Ro'e Katz who is the feature owner

Hi @Heng Tan, Try mounting a directory. With a named volume:

volumes:
      - opa_backup:/opal/backup:rw

or mounting to the host’s fs:

volumes:
      - ./opa_backup:/opal/backup:rw

@Ro'e Katz thanks for your suggestion, I can confirm that mapping to the backup directory rather the folder works 🎉🙏