Skip to content

Conversation

@SniperRus
Copy link

modify Dockerfile by including sqlite into docker image, so no need to install it on a host machine and create volume link to sessions.db

only one thing - we should create a file on a host machine before building a container. just put in console in current directory

touch sessions.db

it creates an empty file so when container created it will update it with a command sqlite3 sessions.db "VACUUM;" inside a container

…tainer

modify Dockerfile and docker-compose.yml by including sqlite3 into docker image, so no need to install it on a host machine
and create volume link to sessions.db

only one thing - we should create a file on a host machine anyway, before building a container.
just put in console in current directory

`touch sessions.db`

it creates an empty file so when container created it will update it with a command `sqlite3 sessions.db "VACUUM;"` inside a container
@FlorianSW
Copy link
Contributor

Without a volume, this would mean that the database is empty when you recreate the container.

I would say that this is not really the intention of a database. It should persist over recreating containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants