Herokuのデプロイに成功したが、heroku run rails db:migrateできない

Question

#実現したいこと
Herokuへのデプロイが成功したので、heroku run rails db:migrateしてアプリが見れる状態にしたい(ログは heroku logs --tailで確認しました)

#環境

• Rails：5.2.4
• DB:Postgres

#試したこと

buildpackを実装して、無事にgit push heroku masterして
すると、remote rejectedの状態がなくなり、無事に$ git push heroku master
して、デプロイに成功しました。

成功した時のコード

remote: Verifying deploy... done.
To https://git.heroku.com/test-ttmanager.git
 * [new branch]      master -> master

しかし、いざ、run heroku db:migrateすると、下記に示すエラー内容が出てしまいました。こちらの原因と、どうしたら解消できるか、調査中ですが、おわかりの方がいらっしゃれば、ご教示いただけないでしょうか？何卒よろしくお願い致します。

#エラー内容

user$ heroku run rails db:migrate
Running rails db:migrate on ⬢ test-ttmanager... up, run.3315 (Free)
Usage:
  rails new APP_PATH [options]

Options:
      [--skip-namespace], [--no-skip-namespace]            # Skip namespace (affects only isolated applications)
  -r, [--ruby=PATH]                                        # Path to the Ruby binary of your choice
                                                           # Default: /app/vendor/ruby-2.6.5/bin/ruby
  -m, [--template=TEMPLATE]                                # Path to some application template (can be a filesystem path or URL)
  -d, [--database=DATABASE]                                # Preconfigure for selected database (options: mysql/postgresql/sqlite3/oracle/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
                                                           # Default: sqlite3
      [--skip-yarn], [--no-skip-yarn]                      # Don't use Yarn for managing JavaScript dependencies
      [--skip-gemfile], [--no-skip-gemfile]                # Don't create a Gemfile
  -G, [--skip-git], [--no-skip-git]                        # Skip .gitignore file
      [--skip-keeps], [--no-skip-keeps]                    # Skip source control .keep files
  -M, [--skip-action-mailer], [--no-skip-action-mailer]    # Skip Action Mailer files
  -O, [--skip-active-record], [--no-skip-active-record]    # Skip Active Record files
      [--skip-active-storage], [--no-skip-active-storage]  # Skip Active Storage files
  -P, [--skip-puma], [--no-skip-puma]                      # Skip Puma related files
  -C, [--skip-action-cable], [--no-skip-action-cable]      # Skip Action Cable files
  -S, [--skip-sprockets], [--no-skip-sprockets]            # Skip Sprockets files
      [--skip-spring], [--no-skip-spring]                  # Don't install Spring application preloader
      [--skip-listen], [--no-skip-listen]                  # Don't generate configuration that depends on the listen gem
      [--skip-coffee], [--no-skip-coffee]                  # Don't use CoffeeScript
  -J, [--skip-javascript], [--no-skip-javascript]          # Skip JavaScript files
      [--skip-turbolinks], [--no-skip-turbolinks]          # Skip turbolinks gem
  -T, [--skip-test], [--no-skip-test]                      # Skip test files
      [--skip-system-test], [--no-skip-system-test]        # Skip system test files
      [--skip-bootsnap], [--no-skip-bootsnap]              # Skip bootsnap gem
      [--dev], [--no-dev]                                  # Setup the application with Gemfile pointing to your Rails checkout
      [--edge], [--no-edge]                                # Setup the application with Gemfile pointing to Rails repository
      [--rc=RC]                                            # Path to file containing extra configuration options for rails command
      [--no-rc], [--no-no-rc]                              # Skip loading of extra configuration options from .railsrc file
      [--api], [--no-api]                                  # Preconfigure smaller stack for API only apps
  -B, [--skip-bundle], [--no-skip-bundle]                  # Don't run bundle install
      [--webpack=WEBPACK]                                  # Preconfigure for app-like JavaScript with Webpack (options: react/vue/angular/elm/stimulus)

Runtime options:
  -f, [--force]                    # Overwrite files that already exist
  -p, [--pretend], [--no-pretend]  # Run but do not make any changes
  -q, [--quiet], [--no-quiet]      # Suppress status output
  -s, [--skip], [--no-skip]        # Skip files that already exist

Rails options:
  -h, [--help], [--no-help]        # Show this help message and quit
  -v, [--version], [--no-version]  # Show Rails version number and quit

Description:
    The 'rails new' command creates a new Rails application with a default
    directory structure and configuration at the path you specify.

    You can specify extra command-line arguments to be used every time
    'rails new' runs in the .railsrc configuration file in your home directory.

    Note that the arguments specified in the .railsrc file don't affect the
    defaults values shown above in this help message.

Example:
    rails new ~/Code/Ruby/weblog

    This generates a skeletal Rails installation in ~/Code/Ruby/weblog.

2020-06-22T13:31:49.000000+00:00 app[api]: Build started by user ※※＊@※※＊.com
2020-06-22T13:35:47.312574+00:00 app[api]: Set LANG, RACK_ENV, RAILS_ENV, RAILS_LOG_TO_STDOUT, RAILS_SERVE_STATIC_FILES, SECRET_KEY_BASE config vars by user ※※＊@※※＊.com
2020-06-22T13:35:47.312574+00:00 app[api]: Release v3 created by user [e-mail]
2020-06-22T13:35:50.833684+00:00 app[api]: Attach DATABASE (@ref:postgresql-opaque-77523) by user ※※＊@※※＊.com
2020-06-22T13:35:50.833684+00:00 app[api]: Running release v4 commands by user ※※＊@※※＊.com
2020-06-22T13:35:50.852147+00:00 app[api]: @ref:postgresql-opaque-77523 completed provisioning, setting DATABASE_URL. by user ※※＊@※※＊.com
2020-06-22T13:35:50.852147+00:00 app[api]: Release v5 created by user ※※＊@※※＊.com
2020-06-22T13:35:51.213419+00:00 app[api]: Release v6 created by user ※※＊@※※＊.com
2020-06-22T13:35:51.213419+00:00 app[api]: Deploy 2e260b4a by user ※※＊@※※＊.com
2020-06-22T13:35:51.231802+00:00 app[api]: Scaled to console@0:Free rake@0:Free web@1:Free by user ※※＊@※※＊.com
2020-06-22T13:35:57.345087+00:00 heroku[web.1]: Starting process with command `bin/rails server -p ${PORT:-5000} -e production`
2020-06-22T13:35:58.000000+00:00 app[api]: Build succeeded
2020-06-22T13:36:00.307868+00:00 app[web.1]: bash: bin/rails: No such file or directory
2020-06-22T13:36:00.405471+00:00 heroku[web.1]: Process exited with status 127
2020-06-22T13:36:00.462719+00:00 heroku[web.1]: State changed from starting to crashed
2020-06-22T13:36:00.464965+00:00 heroku[web.1]: State changed from crashed to starting
2020-06-22T13:36:06.747661+00:00 heroku[web.1]: Starting process with command `bin/rails server -p ${PORT:-5000} -e production`
2020-06-22T13:36:10.116015+00:00 app[web.1]: bash: bin/rails: No such file or directory
2020-06-22T13:36:10.201753+00:00 heroku[web.1]: Process exited with status 127
2020-06-22T13:36:10.265126+00:00 heroku[web.1]: State changed from starting to crashed
2020-06-22T13:38:41.197685+00:00 app[api]: Starting process with command `rails db:migrate` by user　※※＊@※※＊.com
2020-06-22T13:38:45.443569+00:00 heroku[run.3315]: State changed from starting to up
2020-06-22T13:38:45.503484+00:00 heroku[run.3315]: Awaiting client
2020-06-22T13:38:45.528062+00:00 heroku[run.3315]: Starting process with command `rails db:migrate`
2020-06-22T13:38:49.972027+00:00 heroku[run.3315]: Process exited with status 0
2020-06-22T13:38:50.000563+00:00 heroku[run.3315]: State changed from up to complete
2020-06-22T13:44:37.381050+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=test-ttmanager.herokuapp.com request_id=※※※＊-※※※＊ fwd="103.5.140.170" dyno= connect= service= status=503 bytes= protocol=https
2020-06-22T13:44:37.729897+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=test-ttmanager.herokuapp.com request_id=01fffd4e-ec3d-478f-84a3-add40e566298 fwd="※＊.※＊.※＊.170" dyno= connect= service= status=※＊ bytes= protocol=https

#追記　回答を受けて、試したこと

deployしたdirにcdしていないようにみえます。

Gemfilや app, config, public, db などのあるdirにcdする操作をその前に行ってください

とあったので、ルートディレクトリから対象のdirに移動して色々試しましたが、結果うまくいきませんでした。何がいけなかったのか？どうしたらいいのか、ご教示頂けますと幸いです。

①対象dirに移動
②念のためheroku appsで確認したが、ちゃんと入っている

== ＊＊@＊＊.com Apps
App 1
App 2
App 3

③移動したdirに、リモートリポジトリ が存在するか確認

***:***(アプリ名) user$ git remote -v
heroku  https://git.heroku.com/(アプリ名).git (fetch)
heroku  https://git.heroku.com/(アプリ名).git (push)

④公式ガイドを元に、再度デプロイし、heroku run db:migrateするが、失敗。

****:(アプリ名) user$ heroku login
heroku: Press any key to open up the browser to login or q to exit: 
Opening browser to https://cli-auth.heroku.com/auth/cli/browser/****-****-****-****-********
Logging in... done
Logged in as ****@***.com
****:(アプリ名)  user$ heroku git:clone -a (アプリ名)
Cloning into '(アプリ名)'...
remote: Counting objects: 707, done.
remote: Compressing objects: 100% (302/302), done.
remote: Total 707 (delta 364), reused 707 (delta 364)
Receiving objects: 100% (707/707), 238.07 KiB | 354.00 KiB/s, done.
Resolving deltas: 100% (364/364), done.
****:(アプリ名)  user$ cd test-ttmanager
****:(アプリ名)  user$ git add .
****:(アプリ名)  user$ git commit -am "make it better"
On branch master
Your branch is up to date with 'heroku/master'.

nothing to commit, working tree clean
****:(アプリ名) user$ git push heroku master
Everything up-to-date
****:(アプリ名) user$ heroku run rails db:migrate
Running rails db:migrate on ⬢ test-ttmanager... up, run.7994 (Free)
Usage:
  rails new APP_PATH [options]
（以下、質問当初と同じエラー）

Answer 1

前回の質問でも回答したのですが、同じ回答を記載しておきます。
https://qiita.com/arekore0/items/eae550bdbcc78eeac082#%E3%81%A9%E3%81%86%E3%82%84%E3%82%89

Gitのリポジトリを再度作り直して、上記のように適切なディレクトリでgit push origin masterする必要があるかと思います。

Comments

[ikutyan46]

no1konwsさん
ご回答ありがとうございます。再度リモートリポジトリを作成し直したところ別の問題が発生しましたので、この質問については終了とします。

お時間頂きありがとうございました！

Answer 2

deployしたdirにcdしていないようにみえます。
Gemfilや app, config, public, db などのあるdirにcdする操作をその前に行ってください

Comments

[ikutyan46]

winterboumさん

ご回答ありがとうございます。ルートディレクトリに、heroku run rails db:migrateを試みていたので、Gemfilや app, config, public, dbなどのあるアプリのdirに移動して、heroku run rails db:migrateしたのですが、結果が質問と同じで、変わりませんでした。

その後、色々試しましたので、後ほど質問を編集致します。今一度ご確認頂けますと幸いです。