It seems that after some time went by the S3 compatible object storage OCI interface can now work with restic directly and not necessary to use rclone. Tests a few months ago this did not work.
Using S3 directly mean we may not have this issue we see when using restic + rclone:
rclone: 2018/11/02 20:04:16 ERROR : data/fa/fadbb4f1d9172a4ecb591ddf5677b0889c16a8b98e5e3329d63aa152e235602e: Didn”t finish writing GET request (wrote 9086/15280 bytes): http2: stream closed
This shows how I setup restic to Oracle OCI object storage(no rclone required).
Current restic env pointing to rclone.conf
##########################################
# more /root/.restic-envexport RESTIC_REPOSITORY="rclone:s3_servers_ashburn:bucket1"export RESTIC_PASSWORD="blahblah"
# more /root/.config/rclone/rclone.conf[s3_servers_phoenix]type = s3env_auth = falseaccess_key_id =secret_access_key =region = us-phoenix-1endpoint = <client-id>.compat.objectstorage.us-phoenix-1.oraclecloud.comlocation_constraint =acl = privateserver_side_encryption =storage_class =[s3_servers_ashburn]type = s3env_auth = falseaccess_key_id =secret_access_key =region = us-ashburn-1endpoint = <client-id>.compat.objectstorage.us-ashburn-1.oraclecloud.comlocation_constraint =acl = privateserver_side_encryption =New restic env pointing to S3 style
###################################
# more /root/.restic-envexport AWS_ACCESS_KEY_ID=export AWS_SECRET_ACCESS_KEY=export RESTIC_REPOSITORY="s3:<client-id>.compat.objectstorage.us-ashburn-1.oraclecloud.com/bucket1"export RESTIC_PASSWORD="blahblah"
# . /root/.restic-env
# /usr/local/bin/restic snapshotsrepository 26e5f447 opened successfully, password is correctID Date Host Tags Directory----------------------------------------------------------------------dc9827fd 2018-08-31 21:20:02 server1 /etccb311517 2018-08-31 21:20:04 server1 /homef65a3bb5 2018-08-31 21:20:06 server1 /var{...}----------------------------------------------------------------------36 snapshots