Skip to content
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

The instructions for running with Docker compose result in a broken installation #3063

Open
pmbrandvold opened this issue Sep 11, 2024 · 2 comments

Comments

@pmbrandvold
Copy link

pmbrandvold commented Sep 11, 2024

I was able to get the script/setup and script/server files to run after changing every reference to "docker-compose" to "docker compose" to reflect how the docker engine calls compose now. However, this resulted in an instance that runs but doesn't have a users table, apparently. After hitting localhost:3000 I can launch a login page that says "We're sorry, but something went wrong.
If you are the application owner check the logs for more information."

The container logs show:

WARN[0000] The "RAILS_ENV" variable is not set. Defaulting to a blank string.
WARN[0000] The "DATABASE_NAME" variable is not set. Defaulting to a blank string.
WARN[0000] /mnt/c/Git/tracks/tracks-2.7.1/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Creating 1/0
 ✔ Container tracks-271-db-1  Running                                                        0.0s
=> Booting Puma
=> Rails 6.1.7.8 application starting in production
=> Run `bin/rails server --help` for more startup options
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Puma starting in single mode...
* Puma version: 6.4.2 (ruby 3.3.5-p100) ("The Eagle of Durango")
*  Min threads: 5
*  Max threads: 5
*  Environment: production
*          PID: 12
* Listening on http://0.0.0.0:3000
Use Ctrl-C to stop
I, [2024-09-11T20:52:29.826583 #12]  INFO -- : [dc906ed2-7054-4701-a358-c6b0d595660c] Started GET "/" for 172.18.0.1 at 2024-09-11 20:52:29 +0000
I, [2024-09-11T20:52:29.840984 #12]  INFO -- : [dc906ed2-7054-4701-a358-c6b0d595660c] Processing by TodosController#index as HTML
I, [2024-09-11T20:52:29.851685 #12]  INFO -- : [dc906ed2-7054-4701-a358-c6b0d595660c] Redirected to http://localhost:3000/login
I, [2024-09-11T20:52:29.851842 #12]  INFO -- : [dc906ed2-7054-4701-a358-c6b0d595660c] Filter chain halted as :login_or_feed_token_required rendered or redirected
I, [2024-09-11T20:52:29.852104 #12]  INFO -- : [dc906ed2-7054-4701-a358-c6b0d595660c] Completed 302 Found in 11ms (Allocations: 1042)
I, [2024-09-11T20:52:29.886677 #12]  INFO -- : [f952f51c-8282-4379-ae4c-e8a375b7d4e6] Started GET "/login" for 172.18.0.1 at 2024-09-11 20:52:29 +0000
I, [2024-09-11T20:52:29.887615 #12]  INFO -- : [f952f51c-8282-4379-ae4c-e8a375b7d4e6] Processing by LoginController#login as HTML
I, [2024-09-11T20:52:29.909408 #12]  INFO -- : [f952f51c-8282-4379-ae4c-e8a375b7d4e6] Completed 500 Internal Server Error in 22ms (ActiveRecord: 2.0ms | Allocations: 2732)
F, [2024-09-11T20:52:29.910507 #12] FATAL -- : [f952f51c-8282-4379-ae4c-e8a375b7d4e6]
[f952f51c-8282-4379-ae4c-e8a375b7d4e6] ActiveRecord::StatementInvalid (Mysql2::Error: Table 'tracks.users' doesn't exist):
[f952f51c-8282-4379-ae4c-e8a375b7d4e6]
[f952f51c-8282-4379-ae4c-e8a375b7d4e6] app/models/user.rb:146:in `no_users_yet?'
[f952f51c-8282-4379-ae4c-e8a375b7d4e6] app/controllers/login_controller.rb:25:in `login'

It's clear there is' a missing table (tracks.users) but as far as the instructions say, things should be working after running the scripts.

Beyond this issue, there's no really effective way for me to run this in something like portainer, because it requires me to run a bunch of separate scripts to manipulate the docker file and container instances. Is there an easier way to do this? I have an old version of tracks working but it's using Stannoe's docker image which is outdated. Ultimately I just want to update my current instance but I'm stuck until I have a way to set things up with the latest code...

@topcu-muhammet
Copy link

Same here. Is there any solution?

@pmbrandvold
Copy link
Author

What would be easier is if I could just use the tracksapp/tracks image, but there's no documentation on how to set that up in a compose stack. It seems as though it requires a database, which makes sense. But there's no documentation on how to set a database up to be used with the tracksapp/tracks image (which is presumably just a frontend? I'm not sure). When I just pull "tracksapp/tracks" and run it, I get an error that seems to be from no user existing yet, but there's no instructions on how to set up a user.

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

No branches or pull requests

2 participants