New Ory Agent Security is now live! Claim your complimentary test drive. Get Started!

Skip to main content

Container image contents

The Ory Enterprise License (OEL) images of Ory Kratos Identities, Ory Hydra Authorization, Ory Keto Permissions, Ory Oathkeeper IAM Proxy, and Ory Talos Secure API Keys contain only the service binary. The binary carries its own root certificate authorities (CAs) and time zone data. The image runs as user and group 65532.

This applies to the default image tags. The -debug tags add a shell and the usual system files. The FIPS images use a Red Hat Universal Base Image.

What the image does not contain​

  • No shell. To open a shell in the container, use the -debug image tag.
  • No /tmp directory.
  • No /etc/passwd or /etc/group file. User and group names do not resolve.
  • No CA bundle file. To trust a private CA, see Trust a private certificate authority.
  • No writable working directory. The working directory is /.

SQLite​

SQLite writes the database file and temporary files. Use an absolute database path on a writable volume, and mount a writable /tmp:

volumes:
- name: data
persistentVolumeClaim:
claimName: kratos-data
- name: tmp
emptyDir: {}
containers:
- name: kratos
env:
- name: DSN
value: sqlite:///var/lib/sqlite/db.sqlite?_fk=true
volumeMounts:
- name: data
mountPath: /var/lib/sqlite
- name: tmp
mountPath: /tmp

With Docker, use --tmpfs /tmp and a volume for the database directory.

Unix sockets​

To set the owner and group of a Unix socket, use numeric IDs, for example owner: "65532". See Unix sockets.