https://www.ory.sh/ logo
Join Slack
Powered by
<@U04UQ68083H> I get the following error when tryi...
# ory-copilot
f
@chilly-king-10285 I get the following error when trying to run Keto with sqlite: unable to open database file: no such file or directory stack_trace:stack trace could not be recovered from error type sqlite3.Error Docker-compose:
Copy code
services:
  keto-migrate:
    build: ./ory/keto
    environment:
      - LOG_LEVEL=debug
      - DSN=sqlite:///var/lib/sqlite/db.sqlite?_fk=true&mode=rwc
    command: -c /home/ory/keto.yml migrate up -y
    restart: on-failure
    volumes:
      - type: volume
        source: keto-sqlite
        target: /var/lib/sqlite
        read_only: false

  keto:
    build: ./ory/keto
    depends_on:
      - keto-migrate
    environment:
      - DSN=sqlite:///var/lib/sqlite/db.sqlite?_fk=true
    command: serve -c /home/ory/keto.yml
    restart: on-failure
    volumes:
      - type: volume
        source: keto-sqlite
        target: /var/lib/sqlite
        read_only: false

volumes:
  keto-sqlite:
b
A message from kapa.ai
The error you're encountering suggests that Keto is unable to open or create the SQLite database file. This could be due to permission issues or the directory not existing. Let's address this issue step by step: 1. First, ensure that you're using the latest version of Ory Keto. The [Keto CLI documentation](https://www.ory.sh/docs/keto/cli/keto) suggests using the most recent version. 2. The error indicates that the database file or its parent directory doesn't exist or is not accessible. In your Docker Compose configuration, you're using a named volume 
keto-sqlite
mounted at 
/var/lib/sqlite
. Make sure this volume is properly created and has the correct permissions. 3. To ensure the directory exists and has the right permissions, you can modify your Docker Compose file to create the directory before running Keto. Add a new service to create the directory:
Copy code
yaml services:   init:     image: busybox     volumes:       - keto-sqlite:/var/lib/sqlite     command: mkdir -p /var/lib/sqlite    keto-migrate:     depends_on:       - init     # ... rest of your keto-migrate configuration    keto:     depends_on:       - init       - keto-migrate     # ... rest of your keto configuration
4. Make sure the 
DSN
environment variable is correctly set. The [Ory deployment documentation](https://www.ory.sh/docs/ecosystem/deployment) suggests using the following format for SQLite:
Copy code
yaml environment:   - DSN=sqlite:///var/lib/sqlite/db.sqlite?_fk=true&mode=rwc
5. If you're still encountering issues, you might want to check if SELinux is enabled on your system. If it is, you may need to use a different Docker Compose file as mentioned in the [Kratos quickstart guide](https://www.ory.sh/docs/kratos/quickstart#clone-ory-kratos-and-run-it-in-docker):
Copy code
docker-compose -f quickstart.yml -f quickstart-selinux.yml -f quickstart-standalone.yml up --build --force-recreate
6. Lastly, ensure that you've run the necessary migrations. The [Keto migration documentation](https://www.ory.sh/docs/keto/cli/keto-migrate-up) suggests running:
Copy code
keto migrate up
This command is included in your 
keto-migrate
service, but make sure it completes successfully before the 
keto
service starts. If you're still experiencing issues after trying these steps, you might want to check the Keto logs for more detailed error messages. If the problem persists, consider reaching out to the Ory community on their [Slack channel](https://www.ory.sh/docs/ecosystem/contributing#ide-tips) for further assistance.
f
Solved it by creating the sqlite folder and setting ownership to the 
ory
user:
Copy code
FROM oryd/keto:v0.12.0-alpha.0
# By creating the sqlite folder as the ory user, the mounted volume will be owned by ory:ory, which
# is required for read/write of SQLite.
USER root
RUN mkdir -p /var/lib/sqlite
RUN chown ory:ory /var/lib/sqlite
VOLUME /var/lib/sqlite
USER ory
2 Views
Open in Slack
PreviousNext
Powered by