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
Run a second version of the api-gateway container with the -r command to try to create a new access token.
The operation fails, giving timeout as the error message.
(Note that the both containers must share the same data volume to persist the clients.db file)
It seems like SQLite locks the database file, so it's not possible to create a new token while the api-gateway is running.
I feel like this is a bug with bolt, or our use of it. It might be due to how docker handles sharing files in volumes between containers, I haven't tried to do this locally.
The text was updated successfully, but these errors were encountered:
To reproduce:
-r
command to try to create a new access token.timeout
as the error message.(Note that the both containers must share the same data volume to persist the
clients.db
file)It seems like SQLite locks the database file, so it's not possible to create a new token while the api-gateway is running.
I feel like this is a bug with bolt, or our use of it. It might be due to how docker handles sharing files in volumes between containers, I haven't tried to do this locally.
The text was updated successfully, but these errors were encountered: