Can't spin up fresh 1Password Connect Docker stack
Hi all,
I am attempting to spin up a new Docker stack per the README. My docker-compose.yml
looks almost identical to the sample (I've simply changed where 1password-credentials.json
exists on the host machine, put the image version into an environment variable, and changed the data volume name):
--- version: "3" services: op-connect-api: image: "1password/connect-api:${OP_CONNECT_VERSION}" ports: - "8080:8080" restart: unless-stopped volumes: - ./settings/1password-credentials.json:/home/opuser/.op/1password-credentials.json:ro - op-connect-data:/home/opuser/.op/data op-connect-sync: image: "1password/connect-api:${OP_CONNECT_VERSION}" restart: unless-stopped volumes: - ./settings/1password-credentials.json:/home/opuser/.op/1password-credentials.json:ro - op-connect-data:/home/opuser/.op/data volumes: op-connect-data:
When I spin these containers up, I see these logs:
op-connect-api_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:46.458180411Z","level":3} op-connect-sync_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:46.531624914Z","level":3} op-connect-api_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:47.462496385Z","level":3} op-connect-sync_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:47.534869274Z","level":3} op-connect-api_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:48.465383772Z","level":3} op-connect-sync_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:48.540599191Z","level":3} op-connect-api_1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2022-01-02T23:05:49.469153832Z","level":3}
...on and on and on. I haven't had any luck searching Google or these forums, so I'm hoping someone can point out where I've gone wrong.
Thanks!
1Password Version: 7.9.2
Extension Version: Not Provided
OS Version: macOS 12.1
Comments
-
OOF, found the mistake: I accidentally instructed the second container (
op-connect-sync
) to use the1password/connect-api
image; using the correct image (1password/connect-sync
), of course, fixes the issue. Watch your copy/paste, friends!0