Receiving an error message on a new configuration on Ubuntu.

Hi, I am trying to get a 1password connect server set up on my Ubuntu linux machine:

Linux UsersDesktop 5.15.0-72-generic #79-Ubuntu SMP Wed Apr 19 08:22:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I created the creds file:
op connect server list
ID NAME STATE
CHFSZBRHQ5DODC5MYUYQM27BZ4 opserver ACTIVE

I have my compose directory set up with:
ls -ld /home/user1/1pass/* /home/user1/1pass
drwxrwxrwx 2 user1 user1 4096 May 26 10:11 /home/user1/1pass
-rw-rw-rw- 1 user1 user1 1133 May 26 09:23 /home/user1/1pass/1password-credentials.json
-rw-rw-rw- 1 user1 user1 494 May 26 10:10 /home/user1/1pass/docker-compose.yaml

My docker-compose file has been updated to have:

version: "3.4"

services:
op-connect-api:
image: 1password/connect-api:latest
ports:
- "8080:8080"
volumes:
- "./1password-credentials.json:/home/user1/1pass/1password-credentials.json"
- "data:/home/user1/1pass/data"
op-connect-sync:
image: 1password/connect-sync:latest
ports:
- "8081:8080"
volumes:
- "./1password-credentials.json:/home/user1/1pass/1password-credentials.json"
- "data:/home/user1/1pass/data"

volumes:
data:

When I run the compose command I get:

~/1pass$ docker-compose up
[+] Running 3/3
✔ Network 1pass_default Created 0.3s
✔ Container 1pass-op-connect-sync-1 Created 1.7s
✔ Container 1pass-op-connect-api-1 Created 1.7s
Attaching to 1pass-op-connect-api-1, 1pass-op-connect-sync-1
1pass-op-connect-sync-1 | {"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2023-05-26T15:39:46.820240095Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) no existing database found, will initialize at /home/opuser/.op/data/1password.sqlite","timestamp":"2023-05-26T15:39:46.821159461Z","level":3}
1pass-op-connect-api-1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2023-05-26T15:39:47.071836203Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) database initialization complete","timestamp":"2023-05-26T15:39:47.111802369Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T15:39:47.11247514Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 500ms), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T15:39:47.11263463Z","level":1}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T15:39:47.613362927Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 1s), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T15:39:47.613591362Z","level":1}
1pass-op-connect-api-1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2023-05-26T15:39:48.072159173Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T15:39:48.614565597Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 2s), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T15:39:48.614787777Z","level":1}
^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Running 2/2
✔ Container 1pass-op-connect-sync-1 Stopped 2.2s
✔ Container 1pass-op-connect-api-1 Stopped 2.2s
canceled
~/1pass$

It repeats this error indefinitely so I control-c'd to stop it for the sample output above. It looks like its trying to use /home/opuser for its composer directory? I saw other tickets here that said they were seeing the same problem, but none of them explained what the actual problem is with any details on how they actually fixed the problem. At least not in a way that I could figure out here. Any ideas on what I've done wrong on this?

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided