-
-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracks 2.6.1 Container won't start after it has ran once #2844
Comments
Which installation method and which commands are you using? |
i am following the Installation guide from this repo: https://github.com/TracksApp/tracks/blob/master/doc/installation.md My DB install script:
My DB Setup script:
My Tracks install script:
|
I'm having the same problem with a Docker container running on UNRAID 6.9.2, using the UNRAID Community Apps feature to install it. It appears to be using this repository: https://hub.docker.com/r/tracksapp/tracks This is the error I get: There is an installation note with the container, which reads:
I successfully executed this command and have not had any issues. A reboot of the host server will restore functionality, but only so long as the container is not stopped. |
I am also experiencing this problem.
The container can be created fine but after stopping and attempting to restart, the following is logged:
Obviously I cannot reinitialise my database as @cosmoneer suggests
|
The container can be reliably rebuilt at anytime using the existing database. |
I had the same issue with the |
You can start the Tracks 2.6.1 Container just once.....after that, it won't start and a 'docker logs tracks' dump will show this error when you try and start it again:
The text was updated successfully, but these errors were encountered: