# This will start with an in memory database.
$ docker run -p 3567:3567 -d supertokens/supertokens-sqlite
You can use your own config.yaml file as a shared volume or pass the key-values as environment variables.
If you do both, only the shared config.yaml file will be considered.
Available environment variables
$ docker run \
-p 3567:3567 \
-v /path/to/sqlite_data:/sqlite_db \
-d supertokens/supertokens-sqlite
config.yaml file, please make sure you store the following key / values:
core_config_version: 0host: "0.0.0.0"sqlite_config_version: 0sqlite_database_folder_location: "/sqlite_db"info_log_path: null (to log in docker logs)error_log_path: null (to log in docker logs)config.yaml file in the container is /usr/lib/supertokens/config.yaml$ docker run \
-p 3567:3567 \
-v /path/to/config.yaml:/usr/lib/supertokens/config.yaml \
-v /path/to/sqlite_data:/sqlite_db \
-d supertokens/supertokens-sqlite
docker logs <container-name> command.info_log_path and error_log_path variables in your config.yaml file (or passing the values asn env variables).$ docker run \
-p 3567:3567 \
-v /path/to/logsFolder:/home/logsFolder \
-e INFO_LOG_PATH=/home/logsFolder/info.log \
-e ERROR_LOG_PATH=/home/logsFolder/error.log \
-v /path/to/sqlite_data:/sqlite_db \
-d supertokens/supertokens-sqlite
The docker container stores SQLite data in /sqlite_db folder. You can mount a shared volume at that path to persist data across docker restarts.
Please refer to our documentation for this.
Content type
Image
Digest
Size
83.7 MB
Last updated
almost 6 years ago
docker pull supertokens/supertokens-sqlite