1Password on Mastodon

1Password Connect Sync silently fails to initialize database.

Hi, I've been trying to deploy a 1Password Connect Sync instance via Portainer on Open Media Vault using the docker-compose.yml file provided on the official docs. However, connect-sync seems to silently fail in creating a database.

3 log_message=(I) starting 1Password Connect Sync ... timestamp=2023-02-05T07:42:41.589666065Z
3 log_message=(I) no existing database found, will initialize at /home/opuser/.op/data/1password.sqlite timestamp=2023-02-05T07:42:41.590238904Z
Error: Server: (failed to OpenDefault), Wrapped: (failed to open db), unable to open database file: no such file or directory
Usage:
  connect-sync [flags]
Flags:
  -h, --help      help for connect-sync
  -v, --version   version for connect-sync
3 log_message=(I) starting 1Password Connect Sync ... timestamp=2023-02-05T07:43:42.190849567Z
3 log_message=(I) no existing database found, will initialize at /home/opuser/.op/data/1password.sqlite timestamp=2023-02-05T07:43:42.191297845Z
Error: Server: (failed to OpenDefault), Wrapped: (failed to open db), unable to open database file: no such file or directory
Usage:
  connect-sync [flags]
Flags:
  -h, --help      help for connect-sync
  -v, --version   version for connect-sync

For reference here is my docker-compose file.

version: "3.4"

services:
  op-connect-api:
    image: 1password/connect-api:latest
    ports:
      - "8080:8080"
    volumes:
      - "/srv/dev-disk-by-uuid-<REDACTED>/personal/jono/1password-credentials.json:/home/opuser/.op/1password-credentials.json"
      - "/srv/dev-disk-by-uuid-<REDACTED>/personal/jono/1password-connect/data:/home/opuser/.op/data"
  op-connect-sync:
    image: 1password/connect-sync:latest
    ports:
      - "8081:8080"
    volumes:
      - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/1password-credentials.json:/home/opuser/.op/1password-credentials.json"
      - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/data:/home/opuser/.op/data"
volumes:
  data:

As far as I can tell, directory ownership isnt an issue here. So Im a bit stumped as to what might be causing this.


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

Comments

  • dekaikiwidekaikiwi
    Community Member
    edited February 5

    Sorry, the docker-compose version above had different paths mapped for volumes of each image. Ive updated op-connect-sync to use the same volumes as op-connect-api however the issue still persists.

    version: "3.4"
    
    services:
      op-connect-api:
        image: 1password/connect-api:latest
        ports:
          - "8080:8080"
        volumes:
          - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/1password-credentials.json:/home/opuser/.op/1password-credentials.json"
          - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/data:/home/opuser/.op/data"
      op-connect-sync:
        image: 1password/connect-sync:latest
        ports:
          - "8081:8080"
        volumes:
          - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/1password-credentials.json:/home/opuser/.op/1password-credentials.json"
          - "/srv/dev-disk-by-uuid-<REDACTED>/config/1password/data:/home/opuser/.op/data"
    volumes:
      data:
    
    

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file