Tracks 2.6.1 Container won't start after it has ran once

[john2exonets]

Tracks 2.6.1 Container won't start after it has ran once

[ZeiP]

Which installation method and which commands are you using?

[john2exonets]

i am following the Installation guide from this repo: https://github.com/TracksApp/tracks/blob/master/doc/installation.md

My DB install script:

docker run -d -p 3306:3306 --name tracks-db -e MYSQL_ROOT_PASSWORD=blank123 -d mariadb

My DB Setup script:

docker run --link tracks-db:db --rm -t -e "DATABASE_PASSWORD=blank123" -e "DATABASE_TYPE=mysql2" -e "DATABASE_PORT=3306" tracksapp/tracks:2.6.1 bin/rake db:reset --trace

My Tracks install script:

docker run -d -p 3000:3000 --name tracks --link tracks-db:db -t tracksapp/tracks:2.6.1

[cosmoneer]

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:
=> Booting Puma
=> Rails 6.0.4.6 application starting in production
=> Run rails server --help for more startup options
A server is already running. Check /app/tmp/pids/server.pid.

There is an installation note with the container, which reads:

NOTE: After installing, you must console into the container and run the following command to initialize the database first!
rake db:reset
After running that command, you should see the database has tables in it and the app should be usable at that point.

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.

[blacktav]

I am also experiencing this problem.
I am using

• the latest tracksapp on docker (tho the problem existed on a previous image as well)
• an external postgreSQL database (14.6)
• an ArchLinux host (updated @ 28/12/2022)

The container can be created fine but after stopping and attempting to restart, the following is logged:

=> Booting Puma
=> Rails 6.0.5.1 application starting in production 
=> Run `rails server --help` for more startup options
A server is already running. Check /app/tmp/pids/server.pid.

Obviously I cannot reinitialise my database as @cosmoneer suggests
When the container is first run-up, it logs this...

=> Booting Puma
=> Rails 6.0.5.1 application starting in production 
=> Run `rails server --help` for more startup options
Puma starting in single mode...
* Puma version: 6.0.0 (ruby 2.7.7-p221) ("Sunflower")
*  Min threads: 5
*  Max threads: 5
*  Environment: production
*          PID: 9
* Listening on http://0.0.0.0:3000
Use Ctrl-C to stop

[blacktav]

The container can be reliably rebuilt at anytime using the existing database.
It is just the start/stop cycle do not function

[nrybowski]

I had the same issue with the /app folder being a volume mounted from the host in the container. Removing the file /app/tmp/pids/server.pid before restarting the container solves the issue.