You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I start the container (with POPULATE_DATABASE='True') wallabag tables get generated and the database file is created (I mounted the /var/www/wallabag/data to a Docker volume to persist state).
However one table (wallabag_internal_setting) seems not to be created and the logs throws errors:
> bin/console cache:clear --no-warmup
[WARNING] Some commands could not be registered:
In ExceptionConverter.php line 52:
An exception occurred while executing a query: SQLSTATE[HY000]: General err
or: 1 no such table: wallabag_internal_setting
In Exception.php line 28:
SQLSTATE[HY000]: General error: 1 no such table: wallabag_internal_setting
Already tried solutions
I already tried to run migrations for the database manually after the container startup by exec-ing into the container and running
/var/www/wallabag/bin/console wallabag:install --env=prod --no-interaction or
Unfortunately I currently have to time to test this out. Won't get back into trying out Wallabag until next year. @Kdecherf Its on you to close this issue or leave open until I have time.
Environment
POPULATE_DATABASE='True'
My
app/config/parameters.yml
is:What steps will reproduce the bug?
Whenever I start the container (with
POPULATE_DATABASE='True'
) wallabag tables get generated and the database file is created (I mounted the/var/www/wallabag/data
to a Docker volume to persist state).However one table (
wallabag_internal_setting
) seems not to be created and the logs throws errors:Already tried solutions
I already tried to run migrations for the database manually after the container startup by
exec
-ing into the container and running/var/www/wallabag/bin/console wallabag:install --env=prod --no-interaction
or/var/www/wallabag/bin/console doctrine:migrations:migrate --env=prod --no-interaction
However this also leads to the already above mentioned error with the
wallabag_internal_setting
table as seen in the following screenshot:The text was updated successfully, but these errors were encountered: